Remote MCP · Endpoint

io.github.capabilityhostprotocol/chp MCP server

No. io.github.capabilityhostprotocol/chp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://capabilityhostprotocol.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.capabilityhostprotocol/chp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
237 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Learn and adopt the Capability Host Protocol — the agentic web's open evidence layer.
Listing
From the official MCP registry (active).
Recent checks of io.github.capabilityhostprotocol/chp
CheckedResultHandshake
1 hour agoHandshake completed237 ms
1 day agoHandshake completed155 ms
3 days agoHandshake completed299 ms
3 days agoHandshake completed893 ms
4 days agoHandshake completed453 ms
5 days agoHandshake completed657 ms
7 days agoHandshake completed167 ms
10 days agoHandshake completed141 ms
12 days agoHandshake completed136 ms
15 days agoHandshake completed175 ms
17 days agoHandshake completed226 ms
19 days agoHandshake completed163 ms
21 days agoHandshake completed139 ms
23 days agoHandshake completed153 ms
25 days agoHandshake completed124 ms
26 days agoHandshake completed137 ms
28 days agoHandshake completed163 ms
29 days agoHandshake completed158 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/chp and makes no claim about it beyond what these checks measured.