Remote MCP · Endpoint
CrossingKey MCP MCP server
No. CrossingKey MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.crossingkeyintelligence.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.crossingkeyintelligence/crossingkey-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 298 ms
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 82.4% from 17 checks
- Described by its publisher as
- Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 298 ms |
| 2 days ago | Handshake completed | 287 ms |
| 4 days ago | Handshake completed | 205 ms |
| 5 days ago | Handshake completed | 297 ms |
| 7 days ago | Handshake completed | 488 ms |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Handshake completed | 2.54 s |
| 12 days ago | Handshake completed | 159 ms |
| 13 days ago | Handshake completed | 203 ms |
| 15 days ago | Handshake completed | 301 ms |
| 16 days ago | Handshake completed | 543 ms |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Handshake completed | 124 ms |
| 20 days ago | Handshake completed | 135 ms |
| 21 days ago | Handshake completed | 164 ms |
| 22 days ago | Handshake completed | 178 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 CrossingKey MCP and makes no claim about it beyond what these checks measured.