x402-agent-tollbooth
Related Servers
Alternatives to x402-agent-tollbooth
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server providing 50+ crypto, market intelligence, and AI inference endpoints with x402 pay-per-request micropayments on Base.2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProduction-grade Model Context Protocol (MCP) server delivering paywalled Web3 micro-services powered by autonomous x402 payment challenges on Base Mainnet.-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server exposing 10 curated tools for AI agents, providing crypto trading signals, on-chain analysis, and web utilities via pay-per-call x402 endpoints on the Base network.MIT

tereno-mcpofficial
AlicenseNot gradedqualityBmaintenanceMCP server for verifying blockchain safety on Base via x402, with free pricing/receipt tools and paid per-call guard, contract, and metadata checks settled in USDC.34 npmMIT- FlicenseNot gradedqualityBmaintenanceA small, autonomous, pay-per-call MCP server that AI agents discover and pay for per call, with revenue landing directly in a USDC wallet on Base via the x402 payment protocol.-
TDQS
Scored across 9 tools
Most tools target distinct resources (llm, wallet, memory, market, token), but the contract.audit / contract.patch / contract.auditTeaser cluster overlaps heavily: patch includes auditing, and auditTeaser is an explicitly degraded version of audit, so an agent may struggle to pick between them.
Nearly all tools follow a clean namespace.action pattern (llm.query, contract.audit, wallet.profile, memory.store), with only contract.auditTeaser breaking the convention by cramming a modifier into the verb slot instead of using a separate action.
Nine tools is well within the ideal 3-15 range, and each represents a discrete paid service rather than a redundant wrapper, so the set feels appropriately scoped.
Memory has store/retrieve but no update/delete, and there is no discovery, pricing, or payment/balance tool despite the whole server being an x402 tollbooth, leaving notable lifecycle gaps agents must work around.