CortexCloud MCP server
Commit Nov 5, 2026Provides AI agents with pay-per-call on-chain data including token intelligence, wallet analytics, risk assessment, and NFT ownership.
Also known as jonahthan433/cortexcloud-mcp, cortexcloud-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.5.0
- Last commit
- Nov 5, 2026
- License
- MIT
What is CortexCloud MCP?
CortexCloud provides AI agents with pay-per-call on-chain data including token intelligence, wallet analytics, risk assessment, and NFT ownership.
Summary generated from the project's README
About CortexCloud MCP server
CortexCloud provides AI agents with access to on-chain data through a pay-per-call model. Developers can integrate this server to retrieve token intelligence, wallet analytics, risk assessments, and NFT ownership details. The system operates without requiring API keys, subscriptions, or signups, instead settling payments in USDC on the Base network via x402.
Users can connect using a remote HTTP setup for a hosted experience or a local stdio bridge via npx. The server offers 17 tools, including paid functions like cortex_token_intel, cortex_whale_alerts, and cortex_token_risk, alongside free tools like cortex_capabilities and cortex_prices. Paid calls return a challenge containing price and payment details if no signature is provided. To complete a transaction, the client signs an EIP-3009 USDC authorization and includes the payment-signature header in the request.
What you can do with it
- 1Analyze token securityAsk the agent to evaluate the risk profile of a specific cryptocurrency using specialized intelligence tools.
- 2Monitor large holder movementsRequest real-time alerts regarding significant transactions made by whale wallets.
- 3Compare cross-chain dataPerform a comparative analysis of data across different blockchain networks.
Written from the project's README. Every use case is checked against a quote from it.
How to install CortexCloud MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall CortexCloud MCP in Claude Code
$ claude mcp add --transport http cortexcloud-mcp https://api.cortexcloud.org/mcpInstall CortexCloud MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cortexcloud-mcp": {
"url": "https://api.cortexcloud.org/mcp"
}
}
}Install CortexCloud MCP in VS Code
.vscode/mcp.json
{
"servers": {
"cortexcloud-mcp": {
"type": "http",
"url": "https://api.cortexcloud.org/mcp"
}
}
}Install CortexCloud MCP in VS Code CLI
$ code --add-mcp '{"name":"cortexcloud-mcp","type":"http","url":"https://api.cortexcloud.org/mcp"}'Install CortexCloud MCP in Codex
$ codex mcp add cortexcloud-mcp --url https://api.cortexcloud.org/mcpInstall CortexCloud MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.cortexcloud-mcp] url = "https://api.cortexcloud.org/mcp"
Install CortexCloud MCP in Gemini CLI
$ gemini mcp add -s user --transport http cortexcloud-mcp https://api.cortexcloud.org/mcpInstall CortexCloud MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cortexcloud-mcp": {
"url": "https://api.cortexcloud.org/mcp",
"type": "http"
}
}
}Configuration
CORTEXCLOUD_PAYMENT_SIGNATURE
| Name | Description | |
|---|---|---|
| CORTEXCLOUD_PAYMENT_SIGNATURE | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablejonahthan433/cortexcloud-mcp is public and reachablegithub.com/jonahthan433/cortexcloud-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-05github.com/jonahthan433/cortexcloud-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 1003 msPass
README
View on GitHub@cortexcloud.org/mcp
MCP server for CortexCloud — pay-per-call on-chain data and intelligence for AI agents. Token, wallet, risk, whale, balance, NFT, transaction and cross-chain reads, settled in USDC on Base over x402. No API keys, no subscriptions, no signup.
Two ways to connect
1. Remote (recommended). The hosted server speaks Streamable HTTP and is always current:
{
"mcpServers": {
"cortexcloud": {
"type": "http",
"url": "https://api.cortexcloud.org/mcp"
}
}
}
2. stdio bridge. This package, for clients that can only launch a local process:
{
"mcpServers": {
"cortexcloud": {
"command": "npx",
"args": ["-y", "@cortexcloud.org/mcp"]
}
}
}
The bridge is a transport adapter, not a second implementation: it forwards tools/list and tools/call to the hosted server, so tools, schemas and prices can never drift from the API.
Tools
17 tools, served from the live registry:
- Paid (15) —
cortex_token_intel($0.030),cortex_cross_chain_compare($0.040),cortex_whale_alerts($0.030),cortex_token_risk($0.020),cortex_wallet_intel($0.006), and the $0.004 data routes:cortex_token_price,cortex_token_balances,cortex_nft_ownership,cortex_tx_history,cortex_gas_oracle,cortex_block, plus the batch toolscortex_aggregate_balances,cortex_aggregate_nfts,cortex_aggregate_prices,cortex_aggregate_tx_history(up to 20 items per call). - Free (2) —
cortex_capabilities(every route, chain and price) andcortex_prices(the price table).
The authoritative list is always GET https://api.cortexcloud.org/v1/capabilities, or cortex_capabilities over MCP.
How payment works
A paid tool call without payment returns the x402 challenge inside the tool result: price, payee, asset, network, and the endpoint to call. Nothing is charged and no wallet is needed to read it.
To settle, the caller signs an EIP-3009 USDC authorization and replays the request with the payment-signature header. Over MCP the server relays that header to the API unchanged; it holds no funds and never signs. Over stdio, forward an existing signature with:
CORTEXCLOUD_PAYMENT_SIGNATURE=<base64 header> npx -y @cortexcloud.org/mcp
For a complete paid flow from code, use the REST reference client — 402 -> sign -> 200 in one file:
https://api.cortexcloud.org/examples/paid_client.py
Env
| Variable | Default | Meaning |
|---|---|---|
CORTEXCLOUD_BASE |
https://api.cortexcloud.org |
API base; the bridge connects to <base>/mcp |
CORTEXCLOUD_PAYMENT_SIGNATURE |
— | Optional x402 payment header forwarded on every call |
Verified behaviour
initializeadvertises protocol2025-06-18; the upstream server reports version0.5.0.tools/listreturns 17 tools.cortex_capabilitiesreturns the live catalog with no payment.cortex_token_pricewithout payment returns the 402 challenge, not an error.
Links
- API + docs: https://api.cortexcloud.org/docs
- Discovery: x402.json · bazaar · llms.txt
- Latency and prices: https://api.cortexcloud.org/benchmarks.html
MIT licensed.
CortexCloud MCP questions
How do I add CortexCloud MCP to Claude Code?
Run claude mcp add --transport http cortexcloud-mcp https://api.cortexcloud.org/mcp in your terminal. Add --scope user to make it available in every project.
How do I add CortexCloud MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Do I need an API key to use CortexCloud?
No, the service requires no API keys, no subscriptions, and no signup.
What kind of data can I access?
You can access token intelligence, cross-chain comparisons, whale alerts, token risk, wallet intelligence, balances, NFT ownership, and transaction history.
Are there any free tools available?
Yes, the cortex_capabilities and cortex_prices tools are free to use.