Sdk vs X402 Discovery Mcp

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
X
🔗 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/mcpRuntime discovery layer for x402-payable APIs. Agents discover and route to pay-per-call x402 endpoints by capability, get quality-ranked results with trust scores (0-100), and pay per query via x402. Includes MCP server, Python SDK, and CLI (npm install -g x402scout).
Quality signal28/100 (Emerging)23/100 (Emerging)
Install pathnpx · highuvx · low
Engagement 3 0 0 6 1 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView SdkView X402 Discovery Mcp
More alternatives to SdkMore alternatives to X402 Discovery McpAggregators category

Other servers like Sdk