Remote MCP · Endpoint

io.github.capabilityhostprotocol/capabilities-txt-registry MCP server

No. io.github.capabilityhostprotocol/capabilities-txt-registry answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://capabilitiestxt.org/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.capabilityhostprotocol/capabilities-txt-registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
745 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Discover what websites across the agentic web can do — query the capabilities.txt registry.
Listing
From the official MCP registry (active).
Recent checks of io.github.capabilityhostprotocol/capabilities-txt-registry
CheckedResultHandshake
1 hour agoHandshake completed745 ms
1 day agoHandshake completed186 ms
3 days agoHandshake completed212 ms
3 days agoHandshake completed761 ms
4 days agoHandshake completed956 ms
5 days agoHandshake completed230 ms
7 days agoHandshake completed198 ms
10 days agoHandshake completed189 ms
12 days agoHandshake completed140 ms
15 days agoHandshake completed173 ms
17 days agoHandshake completed162 ms
19 days agoHandshake completed171 ms
21 days agoHandshake completed217 ms
23 days agoHandshake completed123 ms
25 days agoHandshake completed178 ms
26 days agoHandshake completed177 ms
28 days agoHandshake completed134 ms
29 days agoHandshake completed110 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.capabilityhostprotocol/capabilities-txt-registry and makes no claim about it beyond what these checks measured.