Sairen
Related Servers
Alternatives to Sairen
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceOne remote MCP server with about 260 tools (also split into 11 focused servers, below) for AI agents: https://tanod.dev/mcp. Connection: streamable HTTP and stateless, with no API key, no account and no OAuth. Setup for 20 clients: https://tanod.dev/connect/?src=gh_mcp Docs for agents: https://tanod.dev/llms.txt OpenAPI: https://tanod.dev/openapi.json4270393 npmMIT

warppay402-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to access 28 monetized Web3 developer tools, including web scraping, PDF extraction, smart contract deployment, and cross-chain USDC micropayments via SSE and x402.MIT
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 gradedqualityBmaintenanceEnables AI agents to call 60+ small, fast utility tools with per-call USDC payments on Base or Solana, covering conversions, validation, lookups, media processing, and blockchain data. It requires no account, API key, or subscription, and includes spending limits for safety.109 npmMIT
- 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

AgentBIT MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to call 50+ pay-per-request tools covering onchain and crypto data, web research, security, compliance screening, business intelligence, and infrastructure checks. Payments settle per call in USDC on Base through the x402 protocol with no accounts, API keys, or subscriptions, and the first call is free for new wallets.MIT
TDQS
Scored across 64 tools
The tool set contains multiple explicit aliases and overlapping real tools, e.g. get_dex_price/get_dex_spot_price/get_solana_dex_price, inspect_address/inspect_blockchain_address/check_address_risk, and check_service_health/check_dependency_health/probe_upstream_endpoint. While descriptions help, an agent still faces substantial misselection risk across 64 tools with unclear boundaries between some security, health, and DeFi utilities.
Most names use snake_case, but the convention is mixed: verb_noun (get_dex_price), noun_oracle (bridge_oracle), noun_guard (circuit_breaker_guard), noun_tool (challenge_risk_tool), and awkward alias names like what_is_my_ip_tool. The names remain readable, but there is no single predictable pattern across the set.
64 tools is far beyond a well-scoped agent toolset, especially because many are backward-compatible aliases, niche microservices, or broad domain dispatchers. This creates severe context overhead and makes it hard for an agent to select the right tool.
The inferred domain is a broad autonomous-agent infrastructure and utility toolkit, and it covers many lifecycles well: RFP auctions, task bounty escrow, agent invoicing, scratchpad state, idempotency, DLQ, webhooks, security scanning, and DeFi oracles. Gaps exist, such as no list/delete for scratchpad keys or webhook listeners, but they are minor and often workable via TTLs or companion tools.