Is the Jonahthan433 Cortexcloud MCP server down?

mcp-registry/io.github.jonahthan433/cortexcloud · v0.5.0

Also listed as awesome/jonahthan433/cortexcloud-mcp, glama/jonahthan433/cortexcloud-mcp

healthy
Last checked 2026-10-27 02:01 UTC · handshake 1.1s

As of 2026-10-27 02:01 UTC, the Jonahthan433 Cortexcloud MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 97.4% of Glimind's liveness checks. It had 54 outages in 90 days, with a median recovery of 12 minutes.

uptime (30d checks)
97.4%
checks observed
2,464
outages (90d)
54
tools
17

Pay-per-call QUBO/Ising optimization for AI agents via x402 (USDC on Base). No API keys.

Point your MCP client at this streamable-http endpoint: https://api.cortexcloud.org/mcp

Agent-readiness: D (69/100)

D (69/100): 0 error(s), 4 warning(s) across 17 tool(s); ~2,264 tokens of tool definitions.
Scores higher than 4% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~2,264 tokens per session — lighter than 55% of servers.
65 → 69 since 2026-10-18
no tool-poisoning patterns
Schemas100
Descriptions53
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability75
Stability20

What to fix (5)

17 of 17 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: cortex_aggregate_balances, cortex_aggregate_nfts, cortex_aggregate_prices, cortex_aggregate_tx_history, cortex_block and 12 more

12 parameter(s) across 9 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: cortex_aggregate_balances, cortex_aggregate_nfts, cortex_aggregate_tx_history, cortex_cross_chain_compare, cortex_nft_ownership and 4 more

Reachable 97.4% of the time over the last 30 days; median recovery 12 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

In the last 30 days: 10 tool(s) removed and 4 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jonahthan433%2Fcortexcloud/fixes

cortex_cross_chain_compare 1 change
{
  "name": "cortex_cross_chain_compare",
  "description": "Compare one contract address across up to 5 chains (price, activity, deployment) in one call. x402 paid: $0.040 USDC on Base per call.",
  "inputSchema": {
    "type": "object",
    "required": [
      "contract"
    ],
    "properties": {
      "chains": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "default": [
          "ethereum",
          "base",
          "arbitrum",
          "polygon",
          "optimism"
        ],
        "maxItems": 5
      },
      "contract": {
        "type": "string",
        "pattern": "^0x[0-9a-fA-F]{40}$",
        "description": "Contract address (same address on each chain)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jonahthan433/cortexcloud"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jonahthan433/cortexcloud"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jonahthan433%2Fcortexcloud.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jonahthan433%2Fcortexcloud?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jonahthan433%2Fcortexcloud?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jonahthan433%2Fcortexcloud.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jonahthan433%2Fcortexcloud.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jonahthan433%2Fcortexcloud?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:adc90b7d01dc9f10…, first seen 2026-10-18, included at leaf 21839 of 76,719. Version history · verify what your client received.

Tools (17)

Compare: most reliable data servers · most reliable finance servers · most reliable other servers · most reliable knowledge servers · most reliable blockchain servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Jonahthan433 Cortexcloud MCP server down right now?

As of 2026-10-27 02:01 UTC, the Jonahthan433 Cortexcloud MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 97.4% of Glimind's liveness checks. It had 54 outages in 90 days, with a median recovery of 12 minutes.

How many tools does Jonahthan433 Cortexcloud MCP server provide?

Jonahthan433 Cortexcloud MCP server advertises 17 tools, including cortex_aggregate_balances, cortex_aggregate_nfts, cortex_aggregate_prices, cortex_aggregate_tx_history, cortex_block.

How do I install Jonahthan433 Cortexcloud MCP server?

Point your MCP client at this streamable-http endpoint: https://api.cortexcloud.org/mcp

Is the Jonahthan433 Cortexcloud MCP server safe to connect to an AI agent?

Glimind scanned all 17 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Jonahthan433 Cortexcloud MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve