Liquid 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
L
Liquid
ertad-family
🔗 Aggregators
X
🔗 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).Runtime 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 signal25/100 (Emerging)23/100 (Emerging)
Install pathuvx · highuvx · low
Engagement 2 0 0 2 1 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView LiquidView X402 Discovery Mcp
More alternatives to LiquidMore alternatives to X402 Discovery McpAggregators category

Other servers like Liquid