Skip to main content
Glama
Sign In
tokyo-futuro-mcp

tokyo-futuro-mcp

by TokyoFuturo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to tokyo-futuro-mcp

No user-submitted related servers found.

    Related Servers

    • spirit-cards-mcp

      spirit-cards-mcpofficial

      spiritcards
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to inspect a proof-of-work minted collectible card game on Robinhood Chain — reading live collection stats, card metadata, points leaderboards, staking pool and recent activity, and verifying or grinding valid nonces locally with no wallet, keys, or transactions.
      9
      MIT

    • evmSDK MCP Server

      OxFrancesco
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to interact with Ethereum, Base and configurable EVM chains over stdio using the shared command catalog, covering contract reads, prepared and policy-guarded execution, wallet management, Socket swaps and bridging, simulation, monitoring and saved contracts.
      -

    • @coragentic/mcp

      coragentic
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and clients to manage wallet-owned identity, private per-agent context, swarm coordination, jobs and offerings, policy-gated tool execution, and audit proofs, with Robinhood Chain execution and payment verification support.
      MIT
    • Agent Wallet Gateway

      Agent Wallet Gatewayofficial

      bidglow-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables compatible AI clients to connect to a local Coinbase Agentic Wallet through stdio MCP, so they can read wallet status, public address, Base USDC balance, and saved operations without signing, transferring, trading, or making payments.
      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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have distinct roles (sign_in, link_companion, persona, job_ticket, job_complete), but tokyo_read and tokyo_play are catch-all routers whose contents overlap (e.g. tokyo_read what=jobs vs tokyo_play path=uc/jobs, or daily/status vs daily). An agent must parse long sub-path lists to know which tool to call, and read vs submit for trials is split awkwardly.

    Naming Consistency5/5

    Every tool uses the same tokyo_ prefix with consistent snake_case verb/noun phrasing (tokyo_sign_in, tokyo_trials_submit, tokyo_link_companion, tokyo_job_ticket). The pattern is predictable throughout.

    Tool Count5/5

    Eight tools is well within a reasonable range and each earns its place for a game domain. The router-style read/play tools actually help keep the surface compact rather than exploding into dozens of endpoints.

    Completeness4/5

    The surface covers auth, read-only state, signed game actions, trials submission, companion linking, persona, and the job accept/complete voucher lifecycle. Some lifecycle edges (e.g. unlinking a companion, job posting) are absent but not critical dead ends.

    Resources