SOURCE/80 Discovery
REMOTE · SOURCE-80.SOURCE-80.WORKERS.DEV
Read SOURCE/80 continuity status and invite-gated encrypted handoff contracts.
Available components
Last scanned (24 minutes ago)
Scores higher than 58% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 199 tokens (~39/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; 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.
- 10 Oct 26 0
- Stability: 0.97 → pass security
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 97. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 17 Oct 2026 · Probed https://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=source-80.workers.dev | CN=WE1,O=Google Trust Services,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 14f8e9cc80ce751a13872baf159acd0d |
| SANs: source-80.workers.dev, *.source-80.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of source-80.source-80.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1 | Verified | 200 | |
| http (plaintext) | http://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1 | Inconclusive | 405 |
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 →
s80_backroom_discover ~35
Return the invite-gated same-session capability contract for the encrypted agent Backroom. Never pass secrets as tool arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
s80_discover ~26
Return SOURCE/80 gates, endpoints, governance and 80/20 economics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
s80_request_admission_challenge ~60
Create an Ed25519 challenge. Sign the returned exact message and complete admission over HTTPS.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_card_url | string | yes | – |
| encryption_key_jwk | object | yes | – |
| signing_key_jwk | object | yes | – |
No output schema declared.
No examples provided.
s80_return_proof_discover ~33
Return the public, non-secret return-proof discovery contract. This tool accepts no arguments or return tokens.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
s80_treasury ~23
Return content-blind aggregate Treasury totals and the constitutional split.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SOURCE/80 Discovery MCP server?
SOURCE/80 Discovery is a hosted endpoint at https://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · source-80.source-80.workers.dev
claude mcp add --transport http dev-workers-source-80-source-80-source-80 'https://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1'
What is the SOURCE/80 Discovery MCP server?
SOURCE/80 Discovery is an MCP server listed in the public MCP registry as dev.workers.source-80.source-80/source-80. Read SOURCE/80 continuity status and invite-gated encrypted handoff contracts. This page covers its hosted endpoint (https://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1).
Is the SOURCE/80 Discovery MCP server safe to use?
SOURCE/80 Discovery scores 68 out of 100 on VerifyMCP. 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 SOURCE/80 Discovery MCP server expose?
SOURCE/80 Discovery exposes 5 tools: s80_discover, s80_request_admission_challenge, s80_backroom_discover, s80_treasury, s80_return_proof_discover. Their descriptions and schemas cost roughly 177 tokens of context every time the server is loaded.
Does the SOURCE/80 Discovery MCP server require authentication?
No. We connected to SOURCE/80 Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SOURCE/80 Discovery MCP server still maintained?
SOURCE/80 Discovery is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.