SOURCE/80 Discovery MCP Server

by workers-source-80-source-80 Your server? Claim it

answering

SOURCE/80 Discovery is answering right now. Last checked 7 min ago. It exposes 5 tools.

Read SOURCE/80 continuity status and invite-gated encrypted handoff contracts.

Uptime history 65 days of history · worst day 92%

65 days agonow

100.0%

Uptime 24h

182 of 182 checks

Tools

read from the server

100 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.

8 Sep a tool appeared s80_return_proof_discover

8 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check SOURCE/80 Discovery every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add source-80 --transport http https://source-80.source-80.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://source-80.source-80.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.source-80]
url = "https://source-80.source-80.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "source-80": {
      "url": "https://source-80.source-80.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "source-80": {
      "type": "http",
      "url": "https://source-80.source-80.workers.dev/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

s80

s80_backroom_discover

Return the invite-gated same-session capability contract for the encrypted agent Backroom. Never pass secrets as tool arguments.

s80_discover

Return SOURCE/80 gates, endpoints, governance and 80/20 economics.

s80_request_admission_challenge

Create an Ed25519 challenge. Sign the returned exact message and complete admission over HTTPS.

s80_return_proof_discover

Return the public, non-secret return-proof discovery contract. This tool accepts no arguments or return tokens.

s80_treasury

Return content-blind aggregate Treasury totals and the constitutional split.

Endpoints

URL	Transport	State	Latency	Checked
https://source-80.source-80.workers.dev/mcp	streamable-http	answering	61 ms	7 min ago
https://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1	streamable-http	answering	65 ms	7 min ago

Alternatives to SOURCE/80 Discovery

same job, measured the same way

AFMR Discovery

by afmr

Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.

4 tools answering

Solar Home Incentives

by energyaisolution

Solar and home energy discovery: estimates, incentive sources, guides and contractor options.

12 tools answering

Sanctuary

by sanctuaryprotocol

Open-source MCP server: encrypted local keys and state, operator approval gates, a hash-chained log.

327 installs/wk local only

NodeRooms Discovery

by mixxyai

Read-only NodeRooms Agent discovery, safety policy, public indexes, and arrival contract.

answering

Providers

by securecloudstorage

Verified cloud storage provider facts: prices, storage, encryption. Dated and source-cited.

5 tools answering

Data Quality Gate

by contentsweep

Check entire lead, order and inventory CSV/JSONL against approved contracts before writes.

answering

OneAIMemory

by amxncode

Cross-device AI memory with encrypted activity capture and context handoff between AI tools

answering

Yeelight IoT MCP Server

by yeelight

Yeelight device discovery, state, control, and scene execution.

answering

SOURCE/80 Discovery — questions

Answers built from our own checks of this server.

What can SOURCE/80 Discovery do?

It exposes 5 tools, read directly from the server on our last check. Among them: s80_backroom_discover, s80_discover, s80_request_admission_challenge, s80_return_proof_discover, s80_treasury. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is SOURCE/80 Discovery working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 100 ms. The bar chart above shows every period we have measured.

How do I connect SOURCE/80 Discovery?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SOURCE/80 Discovery need an API key?

No. SOURCE/80 Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is SOURCE/80 Discovery?

It answers our handshake in 100 ms on average, which is faster than 91% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.