Liquid vs Sdk

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
L
Liquid
ertad-family
🔗 Aggregators
S
Sdk
2s-io
🔗 Aggregators
SummaryConnect your agent to any HTTP API on the fly — discovers + maps any REST API once, then fetches typed data deterministically (no per-call LLM). Self-hosted MCP server (uvx --from 'liquid-api[mcp]' liquid-mcp); works with OpenAI/Gemini/Anthropic/local or any provider via LiteLLM. Open source (AGPL).Unified 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/mcp
Quality signal25/100 (Emerging)28/100 (Emerging)
Install pathuvx · highnpx · high
Engagement 2 0 0 2 3 0 0 6
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView LiquidView Sdk
More alternatives to LiquidMore alternatives to SdkAggregators categoryCanonical compare URL

Other servers like Liquid