Supabase
io.github.mcp-dir/supabase-mcp
Your Supabase account in natural language: run SQL, apply migrations, manage tables, storage, edge f
— the operator's own registry description reported
Publisher io.github.mcp-dir · first seen 2026-08-22 · endpoint https://api.mcp.ai/p_supabase
Dependency rating derived
allow — gateway · retrieval-public ● · V1 shows its work ◐
Cluster gateway · distinctiveness 0.324 (typical). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.
🔏 Signed receipt rr_50310e0d3edb6905f3f62856 · 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 (3 shown, 2026-08-23 → 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-08-23 | 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 |
|---|---|---|---|
| retrieval-public | 21 | serves public facts | truth-checkable against a public source — the V-ladder applies in full |
| action | 8 | changes the world | no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions |
| unclassified | 3 | not classifiable from its text | Tier-1 only until its tools describe themselves |
| generative | 2 | 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 B — usable, with rough edges.
| legibility check | tools passing | ok |
|---|---|---|
| name is clear & specific | 35/35 | ✓ |
| has a description | 35/35 | ✓ |
| description is substantive | 35/35 | ✓ |
| parameters are typed | 35/35 | ✓ |
| parameters are described | 5/35 | 5/35 |
35 of 35 tools graded · 35 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:16:37Z | ok_tools | 200 | 156 | 2025-06-18 |
| 2026-08-30T06:16:24Z | ok_tools | 200 | 388 | 2025-06-18 |
| 2026-08-23T06:13:54Z | ok_tools | 200 | 506 | 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/io.github.mcp-dir/supabase-mcp)
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 →