Remote MCP · Endpoint

dev.mcphost/mcphost MCP server

No. dev.mcphost/mcphost answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcphost.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.mcphost/mcphost
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
299 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Listing
From the official MCP registry (active).
Recent checks of dev.mcphost/mcphost
CheckedResultHandshake
1 hour agoHandshake completed299 ms
12 hours agoHandshake completed295 ms
1 day agoHandshake completed301 ms
2 days agoHandshake completed301 ms
4 days agoHandshake completed378 ms
4 days agoHandshake completed292 ms
5 days agoHandshake completed299 ms
6 days agoHandshake completed303 ms
8 days agoHandshake completed295 ms
11 days agoHandshake completed301 ms
13 days agoHandshake completed562 ms
16 days agoHandshake completed301 ms
18 days agoHandshake completed308 ms
20 days agoHandshake completed294 ms
22 days agoHandshake completed313 ms
24 days agoHandshake completed300 ms
26 days agoHandshake completed316 ms
27 days agoHandshake completed302 ms
29 days agoHandshake completed295 ms

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

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 dev.mcphost/mcphost and makes no claim about it beyond what these checks measured.