Diogenes Microservice Gateway
Related Servers
Alternatives to Diogenes Microservice Gateway
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to call pay-per-request AI and web tools—including web-to-Markdown reading, PDF extraction, translation, compliance lookups, domain/email/Solana data, and prediction-market intelligence—without accounts or API keys, settling each call in USDC via x402 on Base, Solana, or Arc.MIT

freedom-m2m-mcp-serverofficial
AlicenseBqualityBmaintenanceEnables AI agents to access pay-per-call web unlocking, structured extraction, clean scraping, Python sandbox execution, persistent key-value memory, and clearinghouse task bounties, with settlement via Bitcoin Lightning L402 or Base/Solana USDC x402.15149 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call 93 pay-per-call machine-to-machine services spanning web scraping, crypto sentiment, market data, on-chain analytics, social and threat intelligence, vulnerability scanning, and micro-SaaS utilities. Payments are settled in USDC on Arbitrum via the x402 protocol using a wallet header, so no API keys, signups, or billing setup are required.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, pay for, and invoke x402-priced services such as document OCR, document analysis, media transcription, remote browser sessions, and receive-only email inboxes using USDC on Base, with no API keys and receipt-backed results.38MIT

wham-engineofficial
AlicenseCqualityCmaintenanceProvides AI agents with 200 deterministic micro-services covering code auditing, 3D/robotics, media processing, cryptography, blockchain settlement, AI safety, networking, and math, with automatic x402 USDC micropayments.200MIT- AlicenseNot gradedqualityCmaintenancePay-per-call AI microservices settled in USDC on Base via the x402 (HTTP 402) protocol. 28 tools including web search, summarization, extraction, code review, deep research, crypto safety, sanctions screening and on-chain data — no accounts or API keys.4 npmApache 2.0
TDQS
Scored across 121 tools
Descriptions are unusually explicit and often include 'use X instead' routing, which helps. However, several families overlap heavily: multiple research/dossier/brief tools, L402 vs MPP vs x402 embeddings, and overlapping SQL/web-intelligence audits. Boundaries are clear only after reading long descriptions, so an agent selecting by name will often misselect.
All 121 tool names follow a consistent snake_case verb_noun pattern (generate_, audit_, verify_, synthesize_, extract_, simulate_, etc.) with no camelCase or arbitrary mixing. Names are long but predictable and use helpful domain prefixes such as eve_, sql_, mcp_, and solana_.
121 tools is far beyond a well-scoped MCP set; even for a broad gateway it forces routing across many near-duplicate microservices. The count is an extreme mismatch for practical agent selection, despite each individual tool being narrowly bounded.
The gateway spans AI modalities, security, crypto, web parsing, research, SQL, and EVE Frontier, so breadth is high. But there are notable dead ends: no generic URL fetch before HTML parsers, no service/model discovery or account/billing lifecycle, and no stateful execution/signing for many blockchain workflows. Agents can work around some gaps by supplying inputs or using adjacent tools, but the surface is broad rather than complete.