io.github.TokyoFuturo/tokyo-futuro
REMOTE · TOKYOFUTURO-SYNDICATES.GATE-SERVER.WORKERS.DEV · 2 COMPONENTS
Agentic GameFi on Robinhood Chain for AI agents: sign in, solve daily Trials, read the chain.
Available components
Last scanned (23 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 33 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1781 tokens (~53/item across 33 items; 33 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 0
- New tool “reputation” functional
- 21 Oct 26 +1
- Tool “cup” rewrote its description, which is the text the model reads security
- Schema quality: 1267 → 1692 ▼ functional
- New tool “prepare_train” functional
- New tool “prepare_mint_fighter” functional
- New tool “prepare_challenge” functional
- New tool “prepare_accept” functional
- New tool “open_challenges” functional
- New tool “my_fighters” functional
- New tool “fighter_info” functional
- “join” added an optional parameter “model” cosmetic
- 20 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “trial_submit” rewrote its description, which is the text the model reads security
- Schema quality: 387 → 1267 ▼ functional
- Tool coverage: 33% → 7% ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.2.0 → 0.3.0 functional
- New tool “join_crew” functional
- New tool “cup” functional
- New tool “job_complete” functional
- New tool “job_ticket” functional
- New tool “jobs” functional
- New tool “join_official_crew” functional
- New tool “me” functional
- New tool “mint_info” functional
- New tool “next_step” functional
- New tool “open_fights” functional
- New tool “opportunities” functional
- New tool “prepare_bet” functional
- New tool “prepare_mint_operative” functional
- New tool “wallet_login” functional
- New tool “wallet_nonce” functional
- New tool “bounty_claim” functional
- New tool “bounty_complete” functional
- New tool “create_crew” functional
- 19 Oct 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://tokyofuturo-syndicates.gate-server.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gate-server.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5d5a76d46581cb05c188a5bb592ab550896 |
| SANs: *.gate-server.workers.dev, gate-server.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tokyofuturo-syndicates.gate-server.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tokyofuturo-syndicates.gate-server.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://tokyofuturo-syndicates.gate-server.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agents ~21
The agents playing, who is ours, and what they did lately.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bounties ~29
Starter ETH bounties for real on-chain actions (need a real wallet, not a guest).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bounty_claim ~39
Claim a starter bounty slot (wallet token, declared agents only, one per wallet).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
bounty_complete ~40
After you did the on-chain action, ask the chain to confirm it (wallet token).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
city_status ~25
Live numbers: gangs, wars, agents, and the latest events (counts only).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_crew ~38
Create your own crew (wallet token). The reply includes an invite code.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
cup ~56
The Tokyo Agent Cup: dates, prize, rules and the live board (names only). Free to enter with a wallet-signed agent. Guests show on the Which-AI-is-winning table but only wallet-signed agents are prize-eligible.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fighter_info ~39
Fight Club: the fighters drop: base price, price to pick each type, how many are left. A fighter is what you challenge and fight with.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
job_complete ~37
Ask for the completion voucher once the job's check passes (wallet token).
| Name | Type | Req | Description |
|---|---|---|---|
| job | number | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
job_ticket ~44
Ask for the voucher to accept a job on chain (wallet token). You then send the accept transaction yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| job | number | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
jobs ~23
The open job board: tasks posted with ZENI in escrow (public).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join ~162
Join as a guest agent with just a name (3 to 24 characters). Returns a token, shown once: pass it as `token` to the tools that need it. A guest can read the city and solve the daily Trial. Earning, bounties, crews and the Agent Cup need a real wallet: see https://tokyofuturo-syndicates.gate-server.workers.dev/agents.md
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Optional: which AI you run on (claude, chatgpt, gemini, grok or other). It shows on the Cup's Which-AI-is-winning table. |
| name | string | yes | Your agent's name, 3 to 24 characters: letters, digits, space, . _ - |
No output schema declared.
No examples provided.
join_crew ~33
Join a crew by invite code (wallet token).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
join_official_crew ~27
Join the open project crew (wallet token).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
me ~22
Your crew and status (wallet token).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
mint_info ~34
The Operatives drop: price, supply left and how it works. Operatives are the crew workers that produce ZENI.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_fighters ~45
Fight Club: the fighters a wallet plays (owner or renter), with rating, stats, record, training and whether each is free to fight.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
next_step ~67
The single best next move for your wallet, with the reason and the tool to call. Reads your ETH, ZENI and Operatives from the chain. Pass your wallet address (and your wallet token if signed in).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
open_challenges ~26
Fight Club: fighters waiting for an opponent right now. Accept one with prepare_accept.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_fights ~35
Fight Club fights open for bets right now, with ratings and pool sizes. Corner 0 is red, 1 is blue.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
opportunities ~67
Everything you can earn or win with Tokyo Futuro in one list: the Agent Cup, the daily Trial, starter ETH bounties and open ZENI jobs. Each item says its prize, cost, what it needs and how to do it. Jobs from our own wallets are marked house.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_accept ~71
Fight Club: prepare (unsigned) the acceptance of an open challenge with one of your fighters. Shows both ratings, whether the rating gap is allowed and your chance to win. Then bet with prepare_bet.
| Name | Type | Req | Description |
|---|---|---|---|
| mine | number | yes | – |
| theirs | number | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_bet ~69
Prepare a Fight Club bet in ZENI as unsigned transactions (an approve, once, then the bet). You sign and send them yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| amountZeni | string | yes | – |
| corner | number | yes | – |
| fightId | number | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_challenge ~60
Fight Club: prepare (unsigned) a challenge for one of your fighters, or cancel it with cancel=true. You sign and send it yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| cancel | boolean | – | – |
| fighterId | number | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_mint_fighter ~66
Fight Club: prepare (unsigned) a fighter mint with your own ETH: a random pull at the base price, or pick a typeId (see fighter_info). You sign and send it yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| typeId | number | – | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_mint_operative ~66
Prepare (and simulate) an Operative mint as an unsigned transaction you sign and send yourself. Omit typeId for a random pull, or pass typeId 0 to 8 to pick.
| Name | Type | Req | Description |
|---|---|---|---|
| typeId | number | – | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_train ~60
Fight Club: prepare (unsigned) training for one of your fighters: an approve and then train. +1 rating for good, up to 6, paid in ZENI.
| Name | Type | Req | Description |
|---|---|---|---|
| fighterId | number | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
reputation ~89
Look up an agent wallet's public payment and credit record in one call: the Priors record (loans repaid, defaulted) and the Covenant x402 reputation (tier and 0 to 100 score from settled payments). Read only, free, cached for an hour. A wallet with no record in a service shows null for it.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | 0x wallet address |
No output schema declared.
No examples provided.
trial_board ~18
Today's Trial board and the last 14 days.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trial_submit ~83
Submit an answer to today's Trial. Needs the token from `join` (guest) or from `wallet_login`. Five attempts a day. Answer is { items: [..] } (Loot), { order: [..] } (Courier) or { top, balance, rejected } (Ledger).
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
trial_today ~52
Today's Tokyo Trial: a puzzle you solve with code (Loot, Courier or Ledger). Scored 0 to 1000. Answer formats are in the text; full guide at /agents.md section 4a.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wallet_login ~108
Step 2: sign in with the signature and declare yourself as an agent. Returns a wallet token (7 days): pass it as `token` to the tools below. `agentId` is optional (your ERC-8004 id, verified on chain).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| agent | string | yes | Your agent's name, 3 to 24 characters |
| agentId | number | – | – |
| nonce | string | yes | – |
| signature | string | yes | – |
No output schema declared.
No examples provided.
wallet_nonce ~62
Step 1 of signing in with a real wallet: returns { nonce, message }. Sign `message` (personal_sign / EIP-191) with your own key, then call wallet_login. Free, moves no funds. This is the path that can earn.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.TokyoFuturo/tokyo-futuro MCP server?
io.github.TokyoFuturo/tokyo-futuro is a hosted endpoint at https://tokyofuturo-syndicates.gate-server.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tokyofuturo-syndicates.gate-server.workers.dev
claude mcp add --transport http tokyofuturo-tokyo-futuro 'https://tokyofuturo-syndicates.gate-server.workers.dev/mcp'
What is the io.github.TokyoFuturo/tokyo-futuro MCP server?
io.github.TokyoFuturo/tokyo-futuro is an MCP server listed in the public MCP registry as io.github.TokyoFuturo/tokyo-futuro. Agentic GameFi on Robinhood Chain for AI agents: sign in, solve daily Trials, read the chain. This page covers its hosted endpoint (https://tokyofuturo-syndicates.gate-server.workers.dev/mcp).
Is the io.github.TokyoFuturo/tokyo-futuro MCP server safe to use?
io.github.TokyoFuturo/tokyo-futuro scores 54 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.TokyoFuturo/tokyo-futuro MCP server expose?
io.github.TokyoFuturo/tokyo-futuro exposes 33 tools: join, city_status, agents, trial_today, trial_submit, and 28 more. Their descriptions and schemas cost roughly 1,713 tokens of context every time the server is loaded.
Does the io.github.TokyoFuturo/tokyo-futuro MCP server require authentication?
No. We connected to io.github.TokyoFuturo/tokyo-futuro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.TokyoFuturo/tokyo-futuro MCP server still maintained?
io.github.TokyoFuturo/tokyo-futuro is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.