Remote MCP · Endpoint

io.github.jonahthan433/cortexcloud MCP server

No. io.github.jonahthan433/cortexcloud answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.cortexcloud.org/mcp

The last check completed an MCP handshake.

Registry name
io.github.jonahthan433/cortexcloud
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
840 ms
Tools exposed
4 tools
Uptime, last 30 days
22.2% from 18 checks
Described by its publisher as
Pay-per-call QUBO/Ising optimization for AI agents via x402 (USDC on Base). No API keys.
Repository
https://github.com/jonahthan433/cortexcloud-mcp
Listing
From the official MCP registry (active).
Recent checks of io.github.jonahthan433/cortexcloud
CheckedResultHandshake
1 hour agoHandshake completed840 ms
2 days agoHandshake completed990 ms
4 days agoHandshake completed1.24 s
6 days agoHandshake completed824 ms
7 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
14 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—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—
23 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—

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

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 io.github.jonahthan433/cortexcloud and makes no claim about it beyond what these checks measured.