Remote MCP · Endpoint
io.github.bitcompare/mcp-server MCP server
No. io.github.bitcompare/mcp-server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.bitcompare.net/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.bitcompare/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.13 s
- Tools exposed
- 21 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Crypto yield data for AI agents: lending, savings, staking, borrowing & stablecoin rates. 18 tools.
- Website
- https://bitcompare.net/mcp
- Repository
- https://github.com/bitcompare/services
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.13 s |
| 2 days ago | Handshake completed | 893 ms |
| 4 days ago | Handshake completed | 718 ms |
| 5 days ago | Handshake completed | 699 ms |
| 7 days ago | Handshake completed | 943 ms |
| 8 days ago | Handshake completed | 719 ms |
| 9 days ago | Handshake completed | 750 ms |
| 12 days ago | Handshake completed | 724 ms |
| 13 days ago | Handshake completed | 740 ms |
| 15 days ago | Handshake completed | 760 ms |
| 16 days ago | Handshake completed | 722 ms |
| 18 days ago | Handshake completed | 721 ms |
| 19 days ago | Handshake completed | 705 ms |
| 20 days ago | Handshake completed | 701 ms |
| 20 days ago | Handshake completed | 706 ms |
| 21 days ago | Handshake completed | 718 ms |
| 22 days ago | Handshake completed | 702 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 io.github.bitcompare/mcp-server and makes no claim about it beyond what these checks measured.