Liquid vs Pulsenetwork 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
🔗 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).One MCP server exposing 66 specialized intelligence APIs (660+ endpoints) — finance, crypto, legal, immigration, healthcare cost, real estate, tax, climate, sports, science, and more — each an x402 pay-per-call tool in USDC on Base and Solana. Includes a discover meta-tool over the whole network and a cross-vertical referral graph. No API keys. npx mcp-pulsenetwork
Quality signal25/100 (Emerging)27/100 (Emerging)
Install pathuvx · highnpx · high
Engagement 2 0 0 2 2 0 0 1
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView LiquidView Pulsenetwork Mcp
More alternatives to LiquidMore alternatives to Pulsenetwork McpAggregators category

Other servers like Liquid