Skip to main content
Glama
mmarubio1

Relaystation

by mmarubio1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Relaystation

No user-submitted related servers found.

    Related Servers

    • gapup-mcp by getgapup

      gapup-mcpofficial

      getgapup
      F
      license
      Not graded
      quality
      D
      maintenance
      100+ 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
      -

    • Arch AI Tools

      Deesmo
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides 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.
      1
      -

    • agentsvc-mcp

      jakobautomation
      F
      license
      Not graded
      quality
      F
      maintenance
      20 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.
      1
      -

    • CallMeter

      dammy
      A
      license
      Not graded
      quality
      C
      maintenance
      Near-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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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'.

    Tool Count5/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources