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
- Website
- https://manycp.com/
- Repository
- https://github.com/dayyad/manycp-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 525 ms |
| 10 days ago | Handshake completed | 975 ms |
| 10 days ago | Handshake completed | 579 ms |
| 11 days ago | Handshake completed | 674 ms |
| 12 days ago | Handshake completed | 703 ms |
| 14 days ago | Handshake completed | 605 ms |
| 14 days ago | Handshake completed | 474 ms |
| 15 days ago | Handshake completed | 672 ms |
| 17 days ago | Handshake completed | 577 ms |
| 19 days ago | Handshake completed | 763 ms |
| 21 days ago | Handshake completed | 312 ms |
| 24 days ago | Handshake completed | 598 ms |
| 26 days ago | Handshake completed | 609 ms |
| 28 days ago | Handshake completed | 547 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.