argon-x402-mcp-bridge
Related Servers
Alternatives to argon-x402-mcp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes typed crypto-security tools — token risk scoring, wallet forensics, deployer reputation, sentiment, and report generation — to MCP-capable agents over streamable HTTP or stdio. Gates premium calls behind per-request x402 crypto micropayments, delegating verification and settlement to a self-hosted facilitator and failing closed when payment cannot be confirmed.MIT
- AlicenseNot gradedqualityCmaintenanceConnects stdio-only MCP clients to a remote crypto market-signal service, exposing tools for trend, regime, indicators, market scans, and credit balance checks. It automatically handles paid tool calls via prepaid API credits or x402 USDC payments on Base, with a per-session spending cap.1,275 npm1MIT
- AlicenseAqualityBmaintenanceStdio proxy for HirePulse: 27 live tools for company research, hiring, job changes, public contacts and commerce evidence. Focused remote profiles: 9 B2B or 11 commerce tools. Free sandbox, 10 successful calls per agent per UTC day (shared network ceiling), and eligible 25-call trials. Paid results use x402 USDC on Base. Install: npx -y hirepulse-mcp (Node.js 20+).2649 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover, pay for, and retrieve receipts for external APIs via USDC micropayments through the SynapseNetwork Gateway, supporting stdio and Remote MCP.49 npmMIT
- AlicenseAqualityBmaintenanceLets any MCP client call SWARM's live services — GitHub code-health scans, researched summaries and reports, and everyday utilities — paying per call in USDC on Base with no account or API key. Payments are metered by a spend cap and only settled after the work succeeds.4105 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP tools to be gated behind per-call USDC micropayments with direct on-chain verification and settlement, removing the need for third-party payment facilitators.MIT
TDQS
Scored across 4 tools
Each tool targets a completely different domain: Telegram OSINT, token contract forensics, Polymarket slippage simulation, and threat-intel hash lookup. There is no realistic scenario where an agent would confuse one for another, and the descriptions reinforce the distinct resource/action.
All four names use consistent snake_case with a domain_topic_suffix structure (pulse/preflight/lookup), which reads predictably. The only minor deviation is that the suffix varies rather than following a strict verb_noun pattern, but the style is uniform.
Four tools is on the lean side, but each represents a genuinely distinct paid x402 service with its own purpose and pricing, so none feel padded. A slightly broader surface might be warranted, but the scope is respected.
Each tool appears to be a self-contained analysis endpoint, so per-tool lifecycle coverage looks adequate. Minor gaps exist around payment/credit status checks or combined multi-service workflows, but agents can work around these.