Remote MCP · Endpoint
com.thecryptoport/cryptoport-port MCP server
No. com.thecryptoport/cryptoport-port answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://cryptoport-mcp.cryptoport-port.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- com.thecryptoport/cryptoport-port
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 641 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Daily board of what crypto YouTube channels said: coin calls, stances, catalysts. Free, no key.
- Website
- https://thecryptoport.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 641 ms |
| 1 day ago | Handshake completed | 604 ms |
| 2 days ago | Handshake completed | 1.64 s |
| 3 days ago | Handshake completed | 750 ms |
| 4 days ago | Handshake completed | 606 ms |
| 5 days ago | Handshake completed | 651 ms |
| 6 days ago | Handshake completed | 684 ms |
| 9 days ago | Handshake completed | 796 ms |
| 12 days ago | Handshake completed | 364 ms |
| 14 days ago | Handshake completed | 1.25 s |
| 16 days ago | Handshake completed | 401 ms |
| 18 days ago | Handshake completed | 647 ms |
| 20 days ago | Handshake completed | 636 ms |
| 22 days ago | Handshake completed | 694 ms |
| 24 days ago | Handshake completed | 711 ms |
| 26 days ago | Handshake completed | 66 ms |
| 27 days ago | Handshake completed | 632 ms |
| 28 days ago | Handshake completed | 548 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 com.thecryptoport/cryptoport-port and makes no claim about it beyond what these checks measured.