Skip to content
Menu

Tokyo Futuro MCP

AI Agents

Is this your project? Claim and verify →

MCP server for Tokyo Futuro, an agentic GameFi project on Robinhood Chain that AI agents can play with their own wallet.

What HEY knows

Building
Shipped this weekShipping: 2 meaningful events in 30 days; latest ship today. Evidence Source

Build Momentum 34How it is measured

Latest ship
Code changes this week (since Mon 19 Oct) · 2 commits · · Code activity
FollowCreate alertTerminal previewView latest ship
Share

Follow puts Tokyo Futuro MCP on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me Tokyo Futuro MCP’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 meaningful events in the last 30 days, the newest 2026-10-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 19 Oct) · 2 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 3 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 19 Oct) · 2 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 3 commitssource:769e668d-ab55-4cf3-9539-a67c3afe554e+1 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubXSources

Latest ship

Checked

Code changes this week (since Mon 19 Oct) · 2 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in tokyofuturo/tokyo-futuro-mcp.

This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

Record ship:42ae3240… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Shared change · Published

Tokyo Futuro MCP was published on HEY with its sources recorded.

Builder status: Shipping.

Observed by HEY on 2026-10-19Source: hey state

Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 10 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Tokyo Futuro MCP — as of 2026-10-19

Is Tokyo Futuro MCP still being built?
DerivedShipping: 2 meaningful events in 30 days; latest ship today. Evidence
What did Tokyo Futuro MCP ship last?
FactCode changes this week (since Mon 19 Oct) · 2 commits — Code activity, today. Evidence
What does HEY not know about Tokyo Futuro MCP?
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs. Details

Build timeline

  1. Code changes, week of 2026-10-12 – 2026-10-18 · 3 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in tokyofuturo/tokyo-futuro-mcp.

    This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Tokyo Futuro MCP? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

4 changes on HEY’s record for Tokyo Futuro MCP: 1 verification change · 1 new project on HEY · 2 weeks of code pushed.

Tokyo Futuro MCP on What changed →

The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 2h ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 2h ago.
  • Published packagesMeasuredRead 2h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources