Remote MCP · Endpoint

SOURCE/80 Discovery MCP server

No. SOURCE/80 Discovery answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://source-80.source-80.workers.dev/mcp?entry=mcp_registry_v1

The last check completed an MCP handshake.

Registry name
dev.workers.source-80.source-80/source-80
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
102 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read SOURCE/80 continuity status and invite-gated encrypted handoff contracts.
Website
https://source-80.source-80.workers.dev/.well-known/source80.json
Listing
From the official MCP registry (active).
Recent checks of SOURCE/80 Discovery
CheckedResultHandshake
1 hour agoHandshake completed102 ms
2 days agoHandshake completed122 ms
4 days agoHandshake completed52 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed57 ms
8 days agoHandshake completed354 ms
9 days agoHandshake completed77 ms
12 days agoHandshake completed34 ms
13 days agoHandshake completed91 ms
15 days agoHandshake completed53 ms
16 days agoHandshake completed99 ms
18 days agoHandshake completed51 ms
19 days agoHandshake completed77 ms
20 days agoHandshake completed48 ms
20 days agoHandshake completed34 ms
21 days agoHandshake completed32 ms
22 days agoHandshake completed531 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with SOURCE/80 Discovery and makes no claim about it beyond what these checks measured.