Index / MCP servers / corpusAI Cloud Pricing

corpusAI Cloud Pricing MCP server

corpusAI Cloud Pricing is a remote MCP server that gives an AI agent 35 tools, among them attestations, azure_eviction, capacity_board. It answers at https://cloud.trycorpus.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 11 November 2026, succeeded.

Status
Answering
Tools
35
Reliability
4 of 4 checks
Response time
167 ms
Transport
streamable HTTP
Last checked
11 November 2026

Cloud spot, on-demand, reserved and GPU rental prices with index fixings, paid per call over x402.

Description as the publisher wrote it.

The 35 tools corpusAI Cloud Pricing offers

ToolWhat it does
attestationsFree. Daily on-chain attestations of the fixing set. One record per store day: the keccak256 of the day's signed fixings file (served at /attest/<day>.json), the Ethereum Attestation Service UID and transaction on Base (eip155:8453), the pu
azure_evictionPaid (0.01 USDC per call). Azure spot eviction-rate history (28-day buckets, sampled daily). Daily samples of the eviction-rate bucket Azure reports per SKU (`0-5`, `5-10`, `10-15`, `15-20`, `20+` percent over the trailing 28 days). Collect
Inputs: region, sku, from, to
capacity_boardPaid (0.10 USDC per call). Every GPU model's capacity stress score for one day, tightest first.
Inputs: day
capacity_headlineFree. Capacity stress score per GPU model for the latest day, score only. Rounded score from 0 (slack) to 100 (tight) per GPU with at least two signals, tightest first, cached ten minutes. The components and their inputs are in the paid /ca
capacity_historyPaid (0.05 USDC per call). Daily capacity stress scores for one GPU model.
Inputs: gpu, from, to
capacity_stressPaid (0.01 USDC per call). Capacity stress score, 0 (slack) to 100 (tight), for one GPU model on one day, with every component. Mean of the components available that day: availability (share of Shadeform and Lambda listings flagged availabl
Inputs: gpu, day
catalogFree. Providers, regions, coverage window and event counts. One row per (provider, region) with raw-event coverage (instance types, events, first/last event) and legacy-history coverage (daily and monthly date ranges), plus `sources`, the l
gpu_indexPaid (0.05 USDC per call). Daily USD per GPU-hour index per provider and market for one GPU model, with hyperscaler spot legs. For each snapshot day and (provider, market): number of quotes and the lowest, median, mean and highest USD per G
Inputs: gpu, from, to
gpu_modelsFree. GPU models with rental quotes, and which providers quote them. Normalized model names (use verbatim as `gpu`), number of providers quoting each, quote counts, first/last snapshot day, the lowest observed USD per GPU-hour, and which hy
gpu_quotesPaid (0.01 USDC per call). Latest rental quotes for one GPU model across neo-clouds, marketplaces and other clouds. One row per quote in each provider's latest daily snapshot: provider, market (`ondemand`, `spot` = interruptible, `bid` = ma
Inputs: gpu, provider, market
gpu_snapshotPaid (0.10 USDC per call). Every GPU model × provider × market: lowest and median USD per GPU-hour in the latest snapshot, plus hyperscaler spot per region.
healthFree. Liveness and store readiness. Returns 200 whenever the server is up. `ready` is false while the store is still ingesting after a restart; paid endpoints answer 503 (and take no payment) until it is true.
index_boardPaid (0.10 USDC per call). Every ticker's fixing for one day in one call.
Inputs: day
index_fixingPaid (0.01 USDC per call). One day's fixing for a ticker: median USD per GPU-hour of eligible quotes, with low, high and count. Quote segments (MKT, AGG, NEO, INT, EXE, HYP) fix from that day's snapshots; the default day is the latest snaps
Inputs: ticker, day
index_historyPaid (0.05 USDC per call). Daily fixings for a ticker over a date range. Quote segments start 2026-09-13. SPOT tickers reach back to the start of the spot series (AWS daily from 2022-05-31 for A100, V100, T4, A10; from 2023-07 for H100), ea
Inputs: ticker, from, to
index_tickersFree. Every index ticker, its segment and definition. Tickers are CX.<MODEL>.<SEGMENT> (for example CX.H100SXM.NEO) or CX.<MODEL>.SPOT.<REGION>. Includes the segment membership lists and the methodology version.
instancesFree. Instance types available in a region. Exact type names with per-type coverage: raw events (`events`, `first_event`, `last_event`; zero/null for types that only exist in the legacy history) and legacy history ranges (`history_daily_fro
Inputs: provider, region, prefix
ondemandPaid (0.01 USDC per call). On-demand list-price history of one instance type. Change-point series: one row per day the on-demand (pay-as-you-go) hourly list price changed; `current` is the price in force. AWS: Linux, shared tenancy, from th
Inputs: provider, region, instance
ondemand_snapshotPaid (0.10 USDC per call). Current on-demand list price of every instance type in a region.
Inputs: provider, region
reservedPaid (0.01 USDC per call). Reserved / reservation price history of one instance type (AWS standard RIs 1y/3y no-upfront/all-upfront; Azure reservations 1y/3y). Effective hourly USD with any upfront amortized over the term, as change-point s
Inputs: provider, region, instance, ri_type
reserved_snapshotPaid (0.10 USDC per call). Current reserved effective hourly price of every instance type and ri_type in a region (AWS or Azure).
Inputs: provider, region
spot_dailyPaid (0.05 USDC per call). Full daily history for one instance type, all eras stitched. One row per UTC day from the earliest data for the type to now. Rows dated before the type's first raw event come from the legacy history (`source` = `p
Inputs: provider, region, instance, from, to
spot_eventsPaid (0.01 USDC per call). Raw spot price-change events for one instance type. Every price change for the type in the window, with exact timestamp, availability zone and product (OS). Sorted by time. Repeated identical prices are dropped by
Inputs: provider, region, instance, from, to, az
spot_hourlyPaid (0.01 USDC per call). Hourly time-weighted OHLC bars for one instance type. Per-zone series are bucketed by UTC hour with time weighting (a price counts for as long as it was in force), then collapsed across zones: open/close/avg are t
Inputs: provider, region, instance, from, to
spot_latestPaid (0.01 USDC per call). Price currently in force per zone and product for one instance type. The most recent event of every (zone, product) series of the type, with its timestamp and age. A price is only meaningful while the provider sti
Inputs: provider, region, instance
spot_monthlyPaid (0.05 USDC per call). Full monthly history for one instance type, back to 2014 for legacy AWS types. Calendar months from the earliest data to now. `months` is the curated series: `uscisi-adjusted` months (2017 to 2022-04, AWS types wi
Inputs: provider, region, instance, from, to, include_archive
spot_snapshotPaid (0.10 USDC per call). Current price of every instance type, zone and product in a whole region, in one call. Bulk snapshot: the most recent event of every series in the region (about 6,000 rows for an AWS region), with timestamp and ag
Inputs: provider, region
statusFree. Freshness of every data source. Per source: last successful snapshot or event, staleness in days, and the public URL it is read from. Use it to decide whether a fixing or quote is current before paying for it.
termPaid (0.05 USDC per call). Term structure per hyperscaler for one GPU model, USD per GPU-hour: spot, on-demand, 1y, 3y. For each hyperscaler with a mapped instance family (see /gpu/models hyperscaler_spot_legs), the median across regions of
Inputs: gpu
term_instancePaid (0.01 USDC per call). Price ladder for one instance type: spot, on-demand, 1-year and 3-year commitments, with discounts. Current prices from our series: spot median across zones (where spot events exist), on-demand list price, and res
Inputs: provider, region, instance
tokens_boardPaid (0.10 USDC per call). Every model's input, output and blended fixing for one day, plus the frontier basket.
Inputs: day
tokens_fixingPaid (0.01 USDC per call). One day's token price fixing for a ticker such as CX.TOK.CLAUDESONNET5.IN. Median across every source and host at the standard tier (batch and free variants excluded). `.IN` and `.OUT` are input and output USD per
Inputs: ticker, day
tokens_historyPaid (0.05 USDC per call). Daily fixings for a token ticker, from the first snapshot (2026-09-14).
Inputs: ticker, from, to
tokens_modelsFree. Every LLM with a token price fixing, its ticker codes and today's price range. Canonical model slugs (for example `claude-sonnet-5`, `gpt-6-astra`, `llama-4-maverick`), their ticker codes, how many sources and hosts list them, and the
tokens_quotesPaid (0.01 USDC per call). Every listed price for one model on one day: each source and hosting provider, USD per million tokens. Rows from the OpenRouter catalog, OpenRouter per-host endpoints (Azure, Amazon Bedrock, Google, Together, Deep
Inputs: model, day

Add corpusAI Cloud Pricing to your AI client

Every block below points at https://cloud.trycorpus.ai/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http corpusai-cloud-pricing https://cloud.trycorpus.ai/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "corpusai-cloud-pricing": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://cloud.trycorpus.ai/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "corpusai-cloud-pricing": {
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "corpusai-cloud-pricing": {
      "type": "http",
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "corpusai-cloud-pricing": {
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "corpusai-cloud-pricing": {
      "serverUrl": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "corpusai-cloud-pricing": {
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: corpusAI Cloud Pricing
version: 0.0.1
schema: v1
mcpServers:
  - name: corpusAI Cloud Pricing
    type: streamable-http
    url: https://cloud.trycorpus.ai/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "corpusai-cloud-pricing": {
      "httpUrl": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "corpusai-cloud-pricing": {
      "type": "http",
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "corpusai-cloud-pricing": {
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fcloud.trycorpus.ai%2Fmcp&type=streamable_http&id=corpusai-cloud-pricing&name=corpusAI%20Cloud%20Pricing

Is corpusAI Cloud Pricing up right now?

It answered our last check on 11 November 2026 in 167 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to corpusAI Cloud Pricing

Questions about corpusAI Cloud Pricing

How many tools does corpusAI Cloud Pricing have?

35, as returned by the server's own tools/list on 16 November 2026: attestations, azure_eviction, capacity_board, capacity_headline, capacity_history, capacity_stress, catalog, gpu_index, and 27 more.

Is corpusAI Cloud Pricing down?

It answered our last check on 11 November 2026 in 167 ms. Over 4 checks since 27 September 2026 it answered 4.

How do I add corpusAI Cloud Pricing to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://cloud.trycorpus.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does corpusAI Cloud Pricing need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.jtraversa. Endpoint host: cloud.trycorpus.ai. ARD identifier: urn:air:io.github.jtraversa:mcp:corpus-cloud-pricing-mcp. First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.