CortexCloud MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP listen port | 3200 |
| CORTEXCLOUD_URL | No | Upstream CortexCloud API base | https://api.cortexcloud.org |
| EVM_PRIVATE_KEY | Yes | Wallet that signs + pays each x402 call. Required. | |
| CORTEXCLOUD_PAYTO | No | Wallet where call revenue settles | 0x5a03…ea143 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cortex_estimate_optimizationA | Analyze an optimization problem for free — returns a decision block: recommended mode/backend, estimated provider cost, USDC price, benchmark evidence. Always call this before paying for cortex_optimize. |
| cortex_optimizeA | Solve a QUBO/Ising optimization problem (x402-paid, USDC on Base). Returns a job_id to poll with cortex_get_job. Prices per run: classical $0.05, hybrid $0.10, quantum $0.85 (charged = max(list, provider cost x 2.0)). Use mode=auto unless you specifically need quantum. |
| cortex_get_jobA | Poll an optimization job by id. Free — returns status, solution, objective, error. |
| cortex_list_backendsA | List solver backends (classical/hybrid/quantum) with availability, per-backend estimated provider cost, effective price, and sellable flag. Free — check this before choosing a quantum backend. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role: estimate analyzes a problem, optimize submits a paid job, get_job polls results, and list_backends shows available solvers. The descriptions clearly separate them, reducing any chance of misselection.
All tools share the 'cortex_' prefix and follow a consistent verb-first snake_case pattern (estimate_optimization, optimize, get_job, list_backends). This makes the toolset predictable and easy to navigate.
With 4 tools, the server covers its core workflow (estimate, solve, poll, list backends) without bloat. The count is well within the ideal range and each tool serves a necessary function for the stated purpose.
The core lifecycle of estimating, starting, and retrieving optimization jobs is fully covered. A minor gap is the lack of job cancellation or history management, but for the intended use case this is not a critical omission.