@true402.dev/mcp-server
Related Servers
Alternatives to @true402.dev/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server providing AI agents access to 38 pay-per-call APIs (LLM, image, code, audio, crypto, web, IPFS) via HTTP 402 micropayments in USDC/USDm.22143 npm1MIT
- FlicenseAqualityCmaintenanceMCP server for a live x402 payment gateway on Base (USDC). Lets AI agents discover, preview for free, then pay per call — with prepaid gasless payments, signed receipts, and delta delivery.7-
- AlicenseAqualityBmaintenanceMCP server that enables AI agents to search, describe, and fetch x402 endpoints on Base or Solana, with automatic USDC micropayments.8MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets your AI coding agent (Claude Code, OpenClaw, Codex, Cursor, etc.) discover and pay on-chain agents registered on ERC-8004, using Coinbase's official x402 protocol. No smart account. No bundler. No relay. Just your EOA, an HTTPS request, and an automatic 402 → sign → retry flow.35MIT
- AlicenseCqualityDmaintenanceMCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.10064 npm1MIT

nanoparse-mcpofficial
AlicenseAqualityBmaintenanceMCP server that enables AI agents to fetch web content as clean, structured Markdown via NanoParse's hosted API, using x402 micropayments in USDC on Base.131 npmMIT
TDQS
Scored across 36 tools
The set spans several domains, but within crypto safety there are explicit duplicates: honeypot is the same check as token_safety, address_risk is the same as address_safety, and token_report/token_dossier overlap heavily with token_safety plus extras. Agents can distinguish SEO vs finance vs crypto at a high level, but multiple overlapping aliases and composite bundles create real misselection risk.
Most names use snake_case, which is good, but the convention is not fully predictable: some tools are nouns (backlinks, serp, quant), some are verb_noun (robots_check, headers_check, tx_preflight), and aliases break the pattern (honeypot vs token_safety, address_risk vs address_safety). Chain-specific suffixes are uneven—Ethereum and BSC get full families, Solana only has token_safety_solana, and Base is unsuffixed.
At 36 tools, this is well above the recommended 3–15 range for a coherent set and exceeds the 25+ threshold for 'too many.' The surface is an aggregator of many unrelated services, so the count feels heavy and invites confusion rather than a well-scoped toolkit.
Coverage is broad across SEO/web, finance calculators, prediction markets, DeFi yields, crypto safety, and LLM access. There are minor parity gaps—Solana lacks address_safety and token_report equivalents, and some chains lack live pull/whale tracking—but agents can work around these for most workflows.