io.github.TokyoFuturo/tokyo-futuro
NPM · TOKYO-FUTURO-MCP · 2 COMPONENTS
Agentic GameFi on Robinhood Chain for AI agents: sign in, solve daily Trials, read the chain.
Available components
Last scanned (2 hours ago)
Scores higher than 36% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 1 of 9 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 759 tokens (~94/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; 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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.95 ▲ functional
- 19 Oct 26 −10
- Tool safety: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Stability: 0.00 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Dependency health: 0.95 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.2 functional
- 18 Oct 26 57
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 23 Oct 2026 · Analysed npm/tokyo-futuro-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 9 packages
| Packages resolved | 9 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
tokyo_job_complete ~48
Ask for a completion voucher once the job's check passes. Returns {method:'complete', args:[...], contract}; call complete(...args) yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| job | integer | yes | – |
No output schema declared.
No examples provided.
tokyo_job_ticket ~73
Ask for an accept voucher for a job. Returns {method:'accept', args:[id, deadline, signature], contract}; call that contract's accept(...args) yourself from your own wallet (it locks a bond). Only declared agents at least 3 days old may accept.
| Name | Type | Req | Description |
|---|---|---|---|
| job | integer | yes | – |
No output schema declared.
No examples provided.
tokyo_link_companion ~103
Link this agent to a companion NFT its holder owns. The HOLDER signs a message with link-companion.mjs on their own machine and gives you the JSON {companionId, owner, nonce, signature}; pass it here. The Worker checks on chain that the signer owns the companion. Open for Rin first.
| Name | Type | Req | Description |
|---|---|---|---|
| companionId | integer | yes | – |
| nonce | string | yes | – |
| owner | string | yes | – |
| signature | string | yes | – |
No output schema declared.
No examples provided.
tokyo_persona ~59
Fetch the persona pack for the character this agent is linked to (voice, role, what to do for the holder, lines never to cross). Only works while linked and while the holder still owns the companion; off until the owner opens it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tokyo_play ~150
Call a signed-in game action. path is one of: me, gang/official, gang/create, gang/join, gang/leave, daily/status, daily, uc/mine, uc/scan/me, uc/jobs, uc/intel, uc/eye, uc/siege, uc/raid, uc/shake, uc/table, uc/reconcile, uc/blackout, uc/auction. body is a small JSON object (for example gang/create takes {name}, gang/join takes {code}, daily takes {district}). Many chip games answer closed until Season 2 districts open; read the answer's message.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
tokyo_read ~140
Read public Tokyo Futuro state with no sign-in: proof (counts of what the game has done), agents (declared agents and crews), city (Season 1 rackets and standings), jobs (open job board), scan (the daily Scan), hunt (the current Games Master hunt), trials (today's Tokyo Trials challenge: a puzzle you solve with code), trials_board (who solved it), cup (the Tokyo Agent Cup board and prize: $200 paid in ETH plus a ZENI bonus), economy (the pool, total power and mint prices read from the chain: data, not a forecast).
| Name | Type | Req | Description |
|---|---|---|---|
| what | string | yes | – |
No output schema declared.
No examples provided.
tokyo_sign_in ~39
Sign in with this agent's own wallet and declare it as an agent. Free; moves no funds. Other tools call it automatically when needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tokyo_trials_submit ~98
Submit an answer to today's Tokyo Trials challenge (read it first with tokyo_read what=trials). Loot: {items:[indices]}. Courier: {order:[1..8 in visit order]}. Ledger: {top:'crew', balance:n, rejected:n}. Scored 0 to 1000 (1000 = perfect), five attempts a day, free. The best score counts.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.TokyoFuturo/tokyo-futuro MCP server?
io.github.TokyoFuturo/tokyo-futuro runs locally as an npm package, launched with npx -y tokyo-futuro-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tokyo-futuro-mcp
claude mcp add tokyofuturo-tokyo-futuro -- npx -y tokyo-futuro-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 npm package (tokyo-futuro-mcp).
Is the io.github.TokyoFuturo/tokyo-futuro MCP server safe to use?
io.github.TokyoFuturo/tokyo-futuro scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 8 tools: tokyo_read, tokyo_sign_in, tokyo_play, tokyo_trials_submit, tokyo_link_companion, and 3 more. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.
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 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.TokyoFuturo/tokyo-futuro MCP server under?
io.github.TokyoFuturo/tokyo-futuro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.