Sdk vs MCPDiscovery

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
S
Sdk
2s-io
🔗 Aggregators
M
MCPDiscovery
particlefuture
🔗 Aggregators
SummaryUnified API for AI agents — 180+ tools across geocoding, weather (NWS), climate stations (NOAA), earthquakes (USGS), tides (NOAA), points of interest (OpenStreetMap), patents (USPTO ODP), US case law (CourtListener / Free Law Project), Federal Register, Wikipedia, scientific papers (arXiv / PubMed / Semantic Scholar), AI summarize / translate / extract / screenshot / image-describe, image compression, DNS / WHOIS, crypto address-validate + EVM gas oracle, OFAC sanctions screening, US Census ACS demographics, airport / ZIP lookup. Sub-cent to a few cents per call in USDC on Base via x402 — no API keys, no signup. npx -y @2sio/mcpMCP of MCPs. Automatic discovery and configure MCP servers on your local machine.
Quality signal28/100 (Emerging)17/100 (Emerging)
Install pathnpx · highnpx · low
Engagement 3 0 0 6 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView SdkView MCPDiscovery
More alternatives to SdkMore alternatives to MCPDiscoveryAggregators category

Other servers like Sdk