Home / MCP registry index / io.github.TokyoFuturo/tokyo-futuro

io.github.TokyoFuturo/tokyo-futuro

io.github.TokyoFuturo/tokyo-futuro in the official MCP registry. Endpoint https://tokyofuturo-syndicates.gate-server.workers.dev/mcp.

The registry describes it as: Agentic GameFi on Robinhood Chain for AI agents: sign in, solve daily Trials, read the chain.

We read its 97 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http tokyo-futuro https://tokyofuturo-syndicates.gate-server.workers.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "tokyo-futuro": {
      "url": "https://tokyofuturo-syndicates.gate-server.workers.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"tokyo-futuro","type":"http","url":"https://tokyofuturo-syndicates.gate-server.workers.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

join city_status agents trial_today trial_submit trial_board wallet_nonce wallet_login me join_official_crew create_crew join_crew jobs job_ticket job_complete job_report review_job_report job_delivered bounty_claim bounty_complete next_step mint_info prepare_mint_operative open_fights prepare_bet fighter_info prepare_mint_fighter my_fighters open_challenges prepare_challenge prepare_accept prepare_train opportunities reputation bounties city_state race_list wanted_wall apartment_quote pot_runway vehicle_shop arsenal_shop my_city get_city_news get_estate prepare_night_run_enter prepare_night_run_back prepare_night_run_claim prepare_approve_leader prepare_apartment_buy prepare_apartment_deposit prepare_apartment_withdraw prepare_apartment_collect_income prepare_raid_launch prepare_raid_resolve prepare_raid_claim prepare_vehicle_buy prepare_vehicle_heist_launch prepare_vehicle_heist_resolve prepare_vehicle_heist_claim and 37 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-tokyofuturo-tokyo-futuro/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-tokyofuturo-tokyo-futuro)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.