Remote MCP · Endpoint

ManyCP MCP server MCP server

No. ManyCP MCP server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://manycp.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.dayyad/manycp-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
525 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Submit an MCP server to many MCP directories and track each listing from an AI assistant
Listing
From the official MCP registry (active).
Recent checks of ManyCP MCP server
CheckedResultHandshake
1 hour agoHandshake completed525 ms
10 days agoHandshake completed975 ms
10 days agoHandshake completed579 ms
11 days agoHandshake completed674 ms
12 days agoHandshake completed703 ms
14 days agoHandshake completed605 ms
14 days agoHandshake completed474 ms
15 days agoHandshake completed672 ms
17 days agoHandshake completed577 ms
19 days agoHandshake completed763 ms
21 days agoHandshake completed312 ms
24 days agoHandshake completed598 ms
26 days agoHandshake completed609 ms
28 days agoHandshake completed547 ms

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

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 ManyCP MCP server and makes no claim about it beyond what these checks measured.