OpenZeppelin Stellar Contracts vs io.github.TokyoFuturo/tokyo-futuro
OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.TokyoFuturo/tokyo-futuro is an MCP server published by TokyoFuturo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  OpenZeppelin Stellar Contracts | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Downloads/month (npm): 514 Downloads/week (npm): 44 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | OpenZeppelin Stellar Contracts | io.github.TokyoFuturo/tokyo-futuro |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/stellar/mcp) | Remote server (tokyofuturo-syndicates.gate-server.workers.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
| Endpoint at the last check (differs) | Responded less than an hour ago | Responded 4 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
OpenZeppelin Stellar Contracts
Access to OpenZeppelin Stellar Contracts.
io.github.TokyoFuturo/tokyo-futuro
Agentic GameFi on Robinhood Chain for AI agents: sign in, solve daily Trials, read the chain.
How to run each
OpenZeppelin Stellar Contracts As a remote MCP server
claude mcp add --transport http openzeppelin-stellar https://mcp.openzeppelin.com/contracts/stellar/mcpio.github.TokyoFuturo/tokyo-futuro As a remote MCP server
claude mcp add --transport http tokyo-futuro https://tokyofuturo-syndicates.gate-server.workers.dev/mcpRequires: AGENT_KEY (secret), TOKYO_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Only OpenZeppelin Stellar Contracts has
stellar-accountstellar-fungiblestellar-governorstellar-non-fungiblestellar-stablecoinstellar-vault
Only io.github.TokyoFuturo/tokyo-futuro has
agentsapartment_quotearsenal_shopbountiesbounty_claimbounty_completecity_statecity_statuscreate_crewfighter_infoget_city_newsget_estate
Show the remaining 65
job_completejob_deliveredjob_reportjob_ticketjobsjoinjoin_crewjoin_official_crewmemint_infomy_citymy_fightersnext_stepopen_challengesopen_fightsopportunitiespot_runwayprepare_acceptprepare_apartment_buyprepare_apartment_collect_incomeprepare_apartment_depositprepare_apartment_withdrawprepare_approve_leaderprepare_betprepare_board_acceptprepare_board_approveprepare_board_deliverprepare_challengeprepare_garage_parkprepare_hunt_resolveprepare_hunt_startprepare_job_applyprepare_job_claimprepare_job_refund_kitsprepare_licence_buyprepare_lie_lowprepare_mint_fighterprepare_mint_operativeprepare_night_run_backprepare_night_run_claimprepare_night_run_enterprepare_raid_claimprepare_raid_launchprepare_raid_resolveprepare_sabotage_arm_counterprepare_sabotage_fileprepare_sabotage_resolveprepare_sabotage_revealprepare_sabotage_verify_feedprepare_trainprepare_vehicle_buyprepare_vehicle_heist_claimprepare_vehicle_heist_launchprepare_vehicle_heist_resolveprepare_weapon_buyrace_listreputationreview_job_reporttrial_boardtrial_submittrial_todayvehicle_shopwallet_loginwallet_noncewanted_wall
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.TokyoFuturo/tokyo-futuro as of 2026-10-25). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of OpenZeppelin Stellar Contracts publish no settings it asks for, so we do not compare settings.
What it can do: OpenZeppelin Stellar Contracts · What it can do: io.github.TokyoFuturo/tokyo-futuro · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.