Remote MCP · Endpoint

com.remote-mcp/registry-mcp MCP server

No. com.remote-mcp/registry-mcp answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://registry-mcp.remote-mcp.com/

The last check completed an MCP handshake.

Registry name
com.remote-mcp/registry-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
305 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
An MCP server that serves informtaion from the official MCP registry
Repository
https://github.com/jaw9c/mcp-registry-mcp
Listing
From the official MCP registry (active).
Recent checks of com.remote-mcp/registry-mcp
CheckedResultHandshake
2 hours agoHandshake completed305 ms
1 day agoHandshake completed492 ms
2 days agoHandshake completed638 ms
3 days agoHandshake completed487 ms
4 days agoHandshake completed467 ms
5 days agoHandshake completed389 ms
7 days agoHandshake completed498 ms
9 days agoHandshake completed602 ms
12 days agoHandshake completed5.16 s
14 days agoHandshake completed1.84 s
16 days agoHandshake completed685 ms
18 days agoHandshake completed398 ms
20 days agoHandshake completed461 ms
22 days agoHandshake completed613 ms
25 days agoHandshake completed436 ms
26 days agoHandshake completed453 ms
27 days agoHandshake completed325 ms
29 days agoHandshake completed698 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.

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 com.remote-mcp/registry-mcp and makes no claim about it beyond what these checks measured.