Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.jonahthan433/cortexcloud

REMOTE · API.CORTEXCLOUD.ORG

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

+41 this week 64 Trust /100

Last scanned (1 hour ago)

Scores higher than 47% of remote servers

Reachable. Last reached 23 Oct 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1373 tokens (~80/item across 17 items; 17 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 0
    • Stability: fail → 0.10 functional
  • 21 Oct 26 +40
    • Stability: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 20 Oct 26 −40
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 19 Oct 26 +40
    • Stability: unverified → fail ▼ security
    • Tool “cortex_ai_chat” was removed ▼ security
    • Tool “cortex_automation_http_request” was removed ▼ security
    • Tool “cortex_automation_transform” was removed ▼ security
    • Tool “cortex_estimate_optimization” was removed ▼ security
    • Tool “cortex_get_job” was removed ▼ security
    • Tool “cortex_list_backends” was removed ▼ security
    • Tool “cortex_optimize” was removed ▼ security
    • Tool “cortex_research_search” was removed ▼ security
    • Tool “cortex_wallet_balances” was removed ▼ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “cortex_token_price” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 71% ▼ functional
    • Schema quality: 60 → 80 ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Server version: 0.4.0 → 0.5.0 functional
    • New tool “cortex_block” functional
    • New tool “cortex_aggregate_balances” functional
    • New tool “cortex_aggregate_nfts” functional
    • New tool “cortex_aggregate_prices” functional
    • New tool “cortex_aggregate_tx_history” functional
    • New tool “cortex_capabilities” functional
    • New tool “cortex_cross_chain_compare” functional
    • New tool “cortex_gas_oracle” functional
    • New tool “cortex_nft_ownership” functional
    • New tool “cortex_prices” functional
    • New tool “cortex_token_balances” functional
    • New tool “cortex_token_intel” functional
    • New tool “cortex_token_risk” functional
    • New tool “cortex_tx_history” functional
    • New tool “cortex_wallet_intel” functional
    • New tool “cortex_whale_alerts” functional
    • “cortex_token_price” added an optional parameter “chain” cosmetic
    • “cortex_token_price” reworded the description of “contract” cosmetic
    • “cortex_token_price” reworded the description of “id” cosmetic
  • 18 Oct 26 0
    • Transport: Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
  • 17 Oct 26 0
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. security
  • 10 Oct 26 0
    • Transport: Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Probed https://api.cortexcloud.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cortexcloud.org CN=WE1,O=Google Trust Services,C=US 8 Sept 2026 8 Dec 2026 ECDSA 256 ECDSA-SHA256 8db7893d012ed8c00eae09df17b048ee
SANs: cortexcloud.org, *.cortexcloud.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.cortexcloud.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
cortexcloud.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.cortexcloud.org/mcp Verified 200
http (plaintext) http://api.cortexcloud.org/mcp HTTPS enforced 301 https://api.cortexcloud.org/mcp
MCP tools · 17 exposed · ~1,293 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cortex_aggregate_balances ~71

Batch ERC-20 balances for many addresses in one call (Alchemy). Priced per constituent lookup: $0.004 USDC per address (1-20 addresses).

NameTypeReqDescription
addressesarrayyes–
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism

No output schema declared.

No examples provided.

cortex_aggregate_nfts ~74

Batch NFT ownership across addresses in one call. Priced per constituent lookup: $0.004 USDC per address (1-20 addresses).

NameTypeReqDescription
addressesarrayyes–
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
page_sizeinteger––

No output schema declared.

No examples provided.

cortex_aggregate_prices ~63

Batch spot USD prices for many coins (CoinGecko). Priced per constituent lookup: $0.004 USDC per id (1-50 ids).

NameTypeReqDescription
idsarrayyesCoinGecko ids, e.g. ['ethereum','usd-coin']

No output schema declared.

No examples provided.

cortex_aggregate_tx_history ~73

Batch normalized transfers across addresses in one call. Priced per constituent lookup: $0.004 USDC per address (1-20 addresses).

NameTypeReqDescription
addressesarrayyes–
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
limitinteger––

No output schema declared.

No examples provided.

cortex_block ~75

Block by number or 'latest' on a chain (Alchemy). x402 paid: $0.004 USDC on Base per call.

NameTypeReqDescription
blockstring–Block number (decimal or 0x hex) or 'latest'
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism

No output schema declared.

No examples provided.

cortex_capabilities ~24

Free: service capabilities, supported chains/providers, payment terms and discovery index.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cortex_cross_chain_compare ~68

Compare one contract address across up to 5 chains (price, activity, deployment) in one call. x402 paid: $0.040 USDC on Base per call.

NameTypeReqDescription
chainsarray––
contractstringyesContract address (same address on each chain)

No output schema declared.

No examples provided.

cortex_gas_oracle ~61

Current base fee + priority fee (gas prices) for a chain (Alchemy). x402 paid: $0.004 USDC on Base per call.

NameTypeReqDescription
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism

No output schema declared.

No examples provided.

cortex_nft_ownership ~77

NFTs owned by a wallet on a chain (Alchemy NFT API). x402 paid: $0.004 USDC on Base per call.

NameTypeReqDescription
addressstringyesEVM wallet address
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
page_sizeinteger––

No output schema declared.

No examples provided.

cortex_prices ~27

Free: complete tool/price table for this MCP gateway (served locally, no upstream call).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cortex_token_balances ~93

ERC-20 token balances for a wallet on a chain (Alchemy Token API). x402 paid: $0.004 USDC on Base per call.

NameTypeReqDescription
addressstringyesEVM wallet address
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
max_tokensinteger––
tokensarray–Optional: restrict to these token contracts

No output schema declared.

No examples provided.

cortex_token_intel ~118

Flagship evidence-backed token profile in one call: deployment, metadata, spot price, 24h change, optional age/liquidity/market-cap, recent activity — every fact carries source + checked_at. x402 paid: $0.030 USDC on Base per call.

NameTypeReqDescription
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
coin_idstring–Optional CoinGecko coin id for age/liquidity/market-cap context
contractstringyesToken contract

No output schema declared.

No examples provided.

cortex_token_price ~116

Spot USD price for a token/coin. Provide 'id' (CoinGecko id, e.g. 'ethereum', 'usd-coin') or 'contract'+'chain'. x402 paid: $0.004 USDC on Base per call.

NameTypeReqDescription
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
contractstring–Token contract (alternative to id)
idstring–CoinGecko coin id, e.g. 'ethereum', 'usd-coin'

No output schema declared.

No examples provided.

cortex_token_risk ~94

Token risk verdict (age, liquidity, contract checks, suspicious-transfer scan) with per-claim evidence. x402 paid: $0.020 USDC on Base per call.

NameTypeReqDescription
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
coin_idstring–Optional CoinGecko coin id for age/liquidity context
contractstringyesToken contract

No output schema declared.

No examples provided.

cortex_tx_history ~85

Normalized transactions for an address on a chain (Alchemy Transfers API). x402 paid: $0.004 USDC on Base per call.

NameTypeReqDescription
addressstringyesEVM address
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
from_blockinteger–Optional starting block
limitinteger––

No output schema declared.

No examples provided.

cortex_wallet_intel ~78

Wallet profile: balances, holdings, recent activity, counterparty relationships (Alchemy). x402 paid: $0.006 USDC on Base per call.

NameTypeReqDescription
addressstringyesEVM wallet address
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
limitinteger––

No output schema declared.

No examples provided.

cortex_whale_alerts ~96

Large-transfer / accumulation alerts with tx hashes + timestamps (Alchemy). Omit 'address' for a chain-wide scan. x402 paid: $0.030 USDC on Base per call.

NameTypeReqDescription
addressstring–Optional wallet to watch
chainstring–Chain: ethereum, base, arbitrum, polygon, optimism
limitinteger––
min_usdnumber––

No output schema declared.

No examples provided.

Install

How do I install the io.github.jonahthan433/cortexcloud MCP server?

io.github.jonahthan433/cortexcloud is a hosted endpoint at https://api.cortexcloud.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.cortexcloud.org

# add to Claude Code
claude mcp add --transport http jonahthan433-cortexcloud 'https://api.cortexcloud.org/mcp'
Common questions

What is the io.github.jonahthan433/cortexcloud MCP server?

io.github.jonahthan433/cortexcloud is an MCP server listed in the public MCP registry as io.github.jonahthan433/cortexcloud. Pay-per-call on-chain data for AI agents: token, wallet, risk, whale, NFT, tx. No API keys. This page covers its hosted endpoint (https://api.cortexcloud.org/mcp).

Is the io.github.jonahthan433/cortexcloud MCP server safe to use?

io.github.jonahthan433/cortexcloud scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.jonahthan433/cortexcloud MCP server expose?

io.github.jonahthan433/cortexcloud exposes 17 tools: cortex_token_balances, cortex_token_price, cortex_nft_ownership, cortex_tx_history, cortex_gas_oracle, and 12 more. Their descriptions and schemas cost roughly 1,293 tokens of context every time the server is loaded.

Does the io.github.jonahthan433/cortexcloud MCP server require authentication?

No. We connected to io.github.jonahthan433/cortexcloud without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.jonahthan433/cortexcloud MCP server still maintained?

io.github.jonahthan433/cortexcloud is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.