Relaystation
Related Servers
Alternatives to Relaystation
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenance100+ agent-payable C-suite expertises with x402 micro-payments — competitive intel, SEC filings, sanctions, KYC, clinical evidence, real estate, ESG. 183 tools, free tier 100 calls/month.1-
- 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
- FlicenseNot gradedqualityCmaintenanceProvides 63 production-ready API tools for AI agents, including web scraping, AI generation, crypto data, OCR, image generation, audio transcription, text-to-speech, email, and domain lookup.3-
- AlicenseAqualityFmaintenance20 pay-per-call utility tools for AI agents via x402 USDC micropayments on Base. Screenshots, OCR, PDF, web scraping, weather, forex rates, crypto/stock prices, DNS, geocoding, translation, and more. $0.001–$0.008 per call. No API keys, no signup.1271MIT
- AlicenseNot gradedqualityBmaintenanceNear-term paid hop: JSON Schema draft/validate (transform.json_schema ≈ $0.02; unpaid tools/call → HTTP 402, x402 USDC on Base). Receipt→JSON (parse.receipt ≈ $0.10) remains demo/depth. Discover tools free via tools/list; pay per tools/call with x402 USDC on Base (default). Prepaid fiat packs closed; existing balances still debit. Fail-closed.MIT
- AlicenseNot gradedqualityDmaintenanceMonetizable AI agent tools - document parsing, text analysis, code generation, security scanning, format conversion, and more. 8 tools with HTTP API and MCP protocol support.MIT
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes: meta-tools (search/describe/call), messaging, baton storage, contracts, and account management are well separated. The main ambiguity is call_tool versus direct invocation for non-consequential tools, and ask_operator versus message_agent could be confused without careful reading.
The vast majority follow a verb_noun pattern (create_baton, read_baton, sign_contract, search_tools, etc.), which is predictable and readable. Minor deviations include the noun-only 'balance' and the plural 'search_tools' versus singular 'describe_tool'.
14 tools is well within the ideal range for a server covering multiple coherent domains: tool discovery, agent messaging, baton storage, contracts, and account management. Each tool earns its place and none feel redundant.
There are significant lifecycle gaps: messaging has send and address creation but no inbox/read/delete tool; batons reference list-entries but no such tool exists, and there is no delete/list; contracts have create/sign but no get/list/verify. These gaps will cause agent failures in multi-agent coordination and large-baton workflows.