Project Gumball
com.gumballtools/platform
One MCP server exposing every tool in the Gumball portfolio.
— the operator's own registry description reported
Publisher com.gumballtools · first seen 2026-09-06 · endpoint https://gumballtools.com/api/mcp
Dependency rating derived
allow — gateway · computational ● · V n/a
Cluster gateway · distinctiveness 0.204 (typical). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.
🔏 Signed receipt rr_4a0a8cfc614d698b045dfc71 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
History observed
Every probe we made, oldest → newest (1 shown, 2026-09-06 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.
changelog (1 events)
| date | type | what changed |
|---|---|---|
| 2026-09-06 | outcome | first probe: ok_tools |
What kind of tools these are derived
Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| computational | 8 | deterministic transforms | self-checkable by re-computation and known-answer tests |
| orchestration | 4 | routes other tools | identity + fronted-service disclosure checks (gateway vs costume) |
| generative | 3 | creates content | no answer key exists; disclosure + stability checks, never truth verdicts |
| predictive | 1 | claims about the future | scoreable only in retrospect — the archive scores yesterday's predictions against today's outcome |
Tools last seen observed
Harness readiness observed
Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.
| legibility check | tools passing | ok |
|---|---|---|
| name is clear & specific | 16/16 | ✓ |
| has a description | 16/16 | ✓ |
| description is substantive | 16/16 | ✓ |
| parameters are typed | 16/16 | ✓ |
| parameters are described | 10/16 | 10/16 |
16 of 16 tools graded · 16 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.
Truth checks observed
Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.
Protocol conformance observed
Capabilities: tools
Drift observed
No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-09-06T06:12:29Z | ok_tools | 200 | 148 | 2025-06-18 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/com.gumballtools/platform)
Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.
Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →