In-depth architectural comparison of the Ncp and Rhumb MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Ncp
Aggregators · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Rhumb
Aggregators · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Ncp if you need specialized Aggregators tools running via a local process. Choose Rhumb if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Ncp when:
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: NCP_API_KEY, NCP_PROJECT_CONFIG.
Primary tools included: Single interface for 50+ MCP tools and skills, Code mode execution with TypeScript, Tool and skill discovery via 'find' command.
Ncp is categorized under Aggregators and uses a local stdio subprocess. In contrast, Rhumb belongs to Aggregators using local stdio subprocess. Select Ncp when you need capabilities focused on aggregators and Rhumb when you require tools for aggregators.
Search indexed Services by what you need them to do
get_score
Get the full AN Score breakdown for a Service: execution quality, access readiness, autonomy level, tier label, and freshness
get_alternatives
Find alternative Services, ranked by AN Score
get_failure_modes
Get known failure patterns, impact severity, and workarounds for a service
discover_capabilities
Browse Capabilities by domain or search text
resolve_capability
Given a Capability ID, and optionally a credential mode, returns ranked providers with health status, cost per call, auth methods, endpoint patterns, execute guidance, and machine-readable recovery fields like recovery_hint.resolve_url, recovery_hint.credential_modes_url, and, when applicable, reco…
execute_capability
Call a Capability through Rhumb Resolve
estimate_capability
Estimate the active execution rail, cost, and health before a Capability call; anonymous direct system-of-record paths also preserve machine-readable execute_readiness handoffs
credential_ceremony
Get step-by-step instructions to obtain API credentials for a Service
check_credentials
Inspect live credential-mode readiness, globally or for a specific Capability
rhumb_list_recipes
List the current published Rhumb Layer 3 recipe catalog
rhumb_get_recipe
Get the full published definition for a Rhumb recipe, including input/output schemas and step topology