Remote MCP · Endpoint

CrossingKey MCP MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://mcp.crossingkeyintelligence.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.crossingkeyintelligence/crossingkey-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
28 tools
Uptime, last 30 days
31.6% from 19 checks
Described by its publisher as
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Website
https://www.crossingkeyintelligence.com/
Repository
https://github.com/crossingkey-holdings/crossingkey-mcp
Listing
From the official MCP registry (active).
Recent checks of CrossingKey MCP
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
19 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
10 days agoHandshake completed214 ms
13 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
21 days agoHandshake completed298 ms
23 days agoHandshake completed287 ms
25 days agoHandshake completed205 ms
27 days agoHandshake completed297 ms
28 days agoHandshake completed488 ms
29 days agoFailed - the server returned an HTTP error—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.