MCP.Market

Cortexcloud MCP server

online · 89% uptime
by jonahthan433·io.github.jonahthan433/cortexcloud·v0.5.0

Pay-per-call on-chain data for AI agents: token, wallet, risk, whale, NFT, tx. No API keys.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Cortexcloud yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cortexcloud tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Cortexcloud compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Uptime
89%
of our recent checks; the typical remote server answers 100%
Response time
570 ms
faster than 25% of 30,031 servers

Release history: 2 versions in the registry since 2026-08-08, latest 2026-10-22, typically one every 75 days.

Install Cortexcloud in Claude Code, Cursor or VS Code

claude mcp add --transport http cortexcloud https://api.cortexcloud.org/mcp
Add to Cursor

Grade history

  • 2026-10-14restoreD → Bscore 83

Cortexcloud: common questions

Is Cortexcloud MCP server safe?
Mostly: it is graded B (83/100). Read the Cortexcloud safety report
How do I install Cortexcloud?
It runs remotely at api.cortexcloud.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Cortexcloud need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cortexcloud maintained?
The last commit was 55 days ago (2026-09-10). The latest release is v0.5.0.
Is Cortexcloud up?
89% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Cortexcloud compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); uptime 89% (of our recent checks; the typical remote server answers 100%); response time 570 ms (faster than 25% of 30,031 servers). Full comparison.