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.

corpusAI Cloud Pricing

REMOTE · CLOUD.TRYCORPUS.AI · 2 COMPONENTS · SCANNED SEP 27

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

70 Trust /100
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 Security74
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5836 tokens (~171/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 1 day we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 34 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 35 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
Install

How do I install the corpusAI Cloud Pricing MCP server?

corpusAI Cloud Pricing is a hosted endpoint at https://cloud.trycorpus.ai/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 · cloud.trycorpus.ai

# add to Claude Code
claude mcp add --transport http jtraversa-corpus-cloud-pricing-mcp 'https://cloud.trycorpus.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "type": "http",
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.jtraversa-corpus-cloud-pricing-mcp]
url = "https://cloud.trycorpus.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "type": "remote",
      "url": "https://cloud.trycorpus.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jtraversa-corpus-cloud-pricing-mcp --url 'https://cloud.trycorpus.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jtraversa-corpus-cloud-pricing-mcp:
    url: "https://cloud.trycorpus.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "Transport": "http",
      "Url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add jtraversa-corpus-cloud-pricing-mcp -t streamable-http -u 'https://cloud.trycorpus.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "type": "http",
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 27 Sept 26 −1
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “spot_snapshot_all” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “capacity_headline” rewrote its description, which is the text the model reads security
    • Tool “capacity_stress” rewrote its description, which is the text the model reads security
    • Tool “catalog” rewrote its description, which is the text the model reads security
    • Tool “gpu_models” rewrote its description, which is the text the model reads security
    • Tool “gpu_quotes” rewrote its description, which is the text the model reads security
    • Tool “health” rewrote its description, which is the text the model reads security
    • Tool “index_fixing” rewrote its description, which is the text the model reads security
    • Tool “index_tickers” rewrote its description, which is the text the model reads security
    • Tool “instances” rewrote its description, which is the text the model reads security
    • Tool “ondemand” rewrote its description, which is the text the model reads security
    • Tool “reserved” rewrote its description, which is the text the model reads security
    • Tool “status” rewrote its description, which is the text the model reads security
    • Tool “term_instance” rewrote its description, which is the text the model reads security
    • Tool “tokens_models” rewrote its description, which is the text the model reads security
    • “capacity_history” reworded the description of “gpu” cosmetic
    • “capacity_stress” reworded the description of “gpu” cosmetic
    • “gpu_index” reworded the description of “gpu” cosmetic
    • “gpu_quotes” reworded the description of “gpu” cosmetic
    • “gpu_quotes” reworded the description of “market” cosmetic
    • “gpu_quotes” reworded the description of “provider” cosmetic
    • “term” reworded the description of “gpu” cosmetic
    • Tool “azure_eviction” changed its title: azure eviction → Azure eviction rates cosmetic
    • Tool “capacity_board” changed its title: capacity board → Capacity stress board cosmetic
    • Tool “capacity_headline” changed its title: capacity headline → Capacity stress headline cosmetic
    • Tool “capacity_history” changed its title: capacity history → Capacity stress history cosmetic
    • Tool “capacity_stress” changed its title: capacity stress → Capacity stress score cosmetic
    • Tool “catalog” changed its title: catalog → Data catalog cosmetic
    • Tool “gpu_index” changed its title: gpu index → GPU rental index cosmetic
    • Tool “gpu_models” changed its title: gpu models → GPU models cosmetic
    • Tool “gpu_quotes” changed its title: gpu quotes → GPU rental quotes cosmetic
    • Tool “gpu_snapshot” changed its title: gpu snapshot → GPU market snapshot cosmetic
    • Tool “health” changed its title: health → Service health cosmetic
    • Tool “index_board” changed its title: index board → Index board cosmetic
    • Tool “index_fixing” changed its title: index fixing → Index fixing cosmetic
    • Tool “index_history” changed its title: index history → Index history cosmetic
    • Tool “index_tickers” changed its title: index tickers → Index tickers cosmetic
    • Tool “instances” changed its title: instances → Instance types in a region cosmetic
    • Tool “ondemand” changed its title: ondemand → On-demand price history cosmetic
    • Tool “ondemand_snapshot” changed its title: ondemand snapshot → Region on-demand snapshot cosmetic
    • Tool “reserved” changed its title: reserved → Reserved price history cosmetic
    • Tool “reserved_snapshot” changed its title: reserved snapshot → Region reserved snapshot cosmetic
    • Tool “spot_daily” changed its title: spot daily → Daily spot history cosmetic
    • Tool “spot_events” changed its title: spot events → Spot price events cosmetic
    • Tool “spot_hourly” changed its title: spot hourly → Hourly spot bars cosmetic
    • Tool “spot_latest” changed its title: spot latest → Current spot price per zone cosmetic
    • Tool “spot_monthly” changed its title: spot monthly → Monthly spot history cosmetic
    • Tool “spot_snapshot” changed its title: spot snapshot → Region spot snapshot cosmetic
    • Tool “status” changed its title: status → Data freshness cosmetic
    • Tool “term” changed its title: term → GPU term structure cosmetic
    • Tool “term_instance” changed its title: term instance → Instance price ladder cosmetic
    • Tool “tokens_board” changed its title: tokens board → LLM token board cosmetic
    • Tool “tokens_fixing” changed its title: tokens fixing → LLM token fixing cosmetic
    • Tool “tokens_history” changed its title: tokens history → LLM token history cosmetic
    • Tool “tokens_models” changed its title: tokens models → LLM models with token prices cosmetic
    • Tool “tokens_quotes” changed its title: tokens quotes → LLM token quotes cosmetic
  • 26 Sept 26 71

    First indexed and scored.

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 27 Sept 2026 · Probed https://cloud.trycorpus.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cloud.trycorpus.ai CN=YE2,O=Let's Encrypt,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA384 62c5d3fccaf05ec8af21b4731ba3085cdba
SANs: cloud.trycorpus.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cloud.trycorpus.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
trycorpus.ai. 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://cloud.trycorpus.ai/mcp Verified 200
http (plaintext) http://cloud.trycorpus.ai/mcp HTTPS enforced 301 https://cloud.trycorpus.ai/mcp
MCP tools · 34 exposed · ~5,678 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
azure_eviction ~185

Paid (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). Collected daily since 2026-09-05; there is no history before the first sample.

NameTypeReqDescription
fromstring–First sample date (inclusive), YYYY-MM-DD. Default: earliest.
regionstringyesAzure region slug: `us-east`, `us-west-2` or `eu-west`.
skustring–Optional SKU name (for example `D2s_v5`). Default: every SKU.
tostring–Last sample date (inclusive), YYYY-MM-DD. Default: latest.

No output schema declared.

No examples provided.

capacity_board ~46

Paid (0.10 USDC per call). Every GPU model's capacity stress score for one day, tightest first.

NameTypeReqDescription
daystring–YYYY-MM-DD; default latest.

No output schema declared.

No examples provided.

capacity_headline ~75

Free. 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 /capacity/stress and /capacity/board.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

capacity_history ~65

Paid (0.05 USDC per call). Daily capacity stress scores for one GPU model.

NameTypeReqDescription
fromstring–YYYY-MM-DD.
gpustringyesNormalized GPU model. Example: H100 SXM
tostring–YYYY-MM-DD.

No output schema declared.

No examples provided.

capacity_stress ~176

Paid (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 available), ionet (deployable ÷ total units on io.net regional SKUs), supply (Vast on-demand offers vs the trailing 30-day median) and spot_ratio (hyperscaler SPOT fixing ÷ HYP fixing, 0.3 → 0 and 0.9 → 100). Each component carries its inputs.

NameTypeReqDescription
daystring–YYYY-MM-DD; default latest.
gpustringyesNormalized GPU model, e.g. `H100 SXM`. Example: H100 SXM

No output schema declared.

No examples provided.

catalog ~91

Free. 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 legend explaining every `source` value returned by /spot/daily and /spot/monthly. Use the `region` values here verbatim in every other call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gpu_index ~212

Paid (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 GPU-hour. Rows with provider `aws-spot` or `gcp-spot` are computed from our own spot price events for the instance family that carries the GPU (time-weighted daily bar divided by GPUs per node, per region), so the neo-cloud market and hyperscaler spot are comparable in one series. Quote history starts 2026-09-13; hyperscaler spot legs reach back to the start of our event data.

NameTypeReqDescription
fromstring–First day (inclusive), YYYY-MM-DD. Default: earliest.
gpustringyesNormalized GPU model from /gpu/models. Example: H100 SXM
tostring–Last day (inclusive), YYYY-MM-DD. Default: latest.

No output schema declared.

No examples provided.

gpu_models ~70

Free. 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 hyperscaler spot instance families map to the model.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gpu_quotes ~298

Paid (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` = marketplace minimum bid, `secure`/`community` = RunPod tiers), GPUs in the quoted unit, USD per GPU-hour, quoted unit price, region where the provider exposes one, and provider-specific detail in `extra` (marketplace host reliability, VRAM, stock status). Sources are each provider's public price feed or page (Vast.ai: the cheapest 64 offers per model, on-demand and bid); /gpu/models lists who quotes each model. Snapshots are taken several times a day.

NameTypeReqDescription
gpustringyesNormalized GPU model from /gpu/models, e.g. `H100 SXM`, `H200`, `B200`, `A100 SXM 80GB`, `L40S`, `RTX 4090`. Example: H100 SXM
marketstring–Restrict to one market (`ondemand`, `spot`, `bid`, `secure`, `community`, `network`, `lease`, `executed`).
providerstring–Restrict to one provider slug as listed by /gpu/models (for example `runpod`, `vast`, `lambda`).

No output schema declared.

No examples provided.

gpu_snapshot ~45

Paid (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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

health ~56

Free. 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

index_board ~47

Paid (0.10 USDC per call). Every ticker's fixing for one day in one call.

NameTypeReqDescription
daystring–Fixing day, YYYY-MM-DD. Default: latest.

No output schema declared.

No examples provided.

index_fixing ~186

Paid (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 snapshot. SPOT fixes from the full UTC day of spot events, so the default is yesterday; SPOT composites carry per-region values and spread_vs_neo. See /methodology for eligibility and aggregation.

NameTypeReqDescription
daystring–Fixing day, YYYY-MM-DD. Default: latest available.
tickerstringyesTicker from /index/tickers, e.g. `CX.H100SXM.NEO` or `CX.H100SXM.SPOT.US-EAST-1`. Example: CX.H100SXM.NEO

No output schema declared.

No examples provided.

index_history ~152

Paid (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), each row carrying its data source.

NameTypeReqDescription
fromstring–First day, YYYY-MM-DD. Default: earliest.
tickerstringyesTicker from /index/tickers. Example: CX.H100SXM.NEO
tostring–Last day, YYYY-MM-DD. Default: today.

No output schema declared.

No examples provided.

index_tickers ~63

Free. 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

instances ~191

Free. 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_from/to`, `history_monthly_from/to`). Optional `prefix` narrows the list (for example `c5.` or `n2-`).

NameTypeReqDescription
prefixstring–Case-sensitive prefix filter on the type name.
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1

No output schema declared.

No examples provided.

ondemand ~278

Paid (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 the AWS Price List API, refreshed weekly, since 2024-01 (every AWS region in /catalog). Azure: every Linux VM SKU from the public Retail Prices API, refreshed daily, since 2026-09-13 (every Azure region in /catalog). GCP: the TITANS-era series (2024 to 2026-08), not refreshed.

NameTypeReqDescription
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1

No output schema declared.

No examples provided.

ondemand_snapshot ~120

Paid (0.10 USDC per call). Current on-demand list price of every instance type in a region.

NameTypeReqDescription
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1

No output schema declared.

No examples provided.

reserved ~340

Paid (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 series per `ri_type` (`ri_1y_no_upfront_standard`, `ri_1y_all_upfront_standard`, `ri_3y_no_upfront_standard`, `ri_3y_all_upfront_standard`; GCP `cud_1y`, `cud_3y`). AWS: Linux, shared tenancy, history back to 2016 for the original three regions, weekly refresh from the AWS Price List API. Azure: all-upfront reservations from the public Retail Prices API, daily, since 2026-09-13. GCP: resource-based committed-use discounts from the Cloud Billing Catalog (vCPU, RAM and GPU commitment SKUs), daily, since 2026-09-13.

NameTypeReqDescription
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerstring–Provider: `aws` (default), `azure` or `gcp`.
regionstringyesRegion slug (for example `us-east-1`, `us-east` for Azure, `us-central1` for GCP). Example: us-east-1
ri_typestring–Restrict to one ri_type.

No output schema declared.

No examples provided.

reserved_snapshot ~100

Paid (0.10 USDC per call). Current reserved effective hourly price of every instance type and ri_type in a region (AWS or Azure).

NameTypeReqDescription
providerstring–Provider: `aws` (default), `azure` or `gcp`.
regionstringyesRegion slug (for example `us-east-1`, `us-east` for Azure, `us-central1` for GCP). Example: us-east-1

No output schema declared.

No examples provided.

spot_daily ~358

Paid (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` = `pauley`: measured 2022-05 to 2024-01 AWS, open/high/low/close present on days the price moved; `titans`: daily average only, 2024 to 2026). Rows from `direct_from` on are time-weighted, zone-collapsed bars from the raw event store (`source` = `direct`, same method as /spot/hourly; `avg` equals the public dashboard value). open/high/low/close are null where the source only has an average.

NameTypeReqDescription
fromstring–Start of the window (inclusive), ISO 8601 UTC. Default: the earliest row for the type.
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1
tostring–End of the window (exclusive), ISO 8601 UTC. Default: now.

No output schema declared.

No examples provided.

spot_events ~397

Paid (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 default (`include_repeats=true` keeps them). Up to `limit` rows; when `truncated` is true, continue with `from` = `next_from`.

NameTypeReqDescription
azstring–Restrict to one availability zone / zone id (for example `use1-az1`). Default: all zones.
fromstring–Start of the window (inclusive), ISO 8601 UTC. Default: 7 days before `to`.
include_repeatsboolean–Keep events whose price equals the previous event of the same (az, product) series. Default false.
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
limitinteger–Maximum rows to return (1 to 10000). Default 5000.
productstring–Restrict to one product / OS string (for example `Linux/UNIX`, `Spot`, `Linux`). Default: all.
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1
tostring–End of the window (exclusive), ISO 8601 UTC. Default: now.

No output schema declared.

No examples provided.

spot_hourly ~277

Paid (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 the median across zones, high is the max, low is the min. Window is capped at 366 days.

NameTypeReqDescription
fromstring–Start of the window (inclusive), ISO 8601 UTC. Default: 30 days before `to`.
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1
tostring–End of the window (exclusive), ISO 8601 UTC. Default: now.

No output schema declared.

No examples provided.

spot_latest ~239

Paid (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 still offers the type; AWS series older than ~10 days are likely retired, GCP/Azure reprice rarely so old timestamps are normal. For every type in a region at once use /spot/snapshot.

NameTypeReqDescription
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1

No output schema declared.

No examples provided.

spot_monthly ~412

Paid (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 with a stable correction factor, average only), then months rolled up from the daily series (`pauley`, `titans`, `direct`: `avg` = median of daily averages, open/close from the first/last day, high/low the extremes, `days` = days covered, `source` = the source covering most days). `archive` (AWS, default on) is the USC/ISI monthly dataset 2014-02 to 2023-12 as published, with open/high/low/close, for 51 legacy types: third-party, mixes OS products, provenance partly unverified; returned separately so it never silently blends into the curated series.

NameTypeReqDescription
fromstring–First month (inclusive), YYYY-MM-DD (use the 1st). Default: earliest.
include_archiveboolean–Include the raw USC/ISI archive rows in `archive`. Default true.
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1
tostring–Last month (inclusive), YYYY-MM-DD. Default: latest.

No output schema declared.

No examples provided.

spot_snapshot ~180

Paid (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 age per row. Same semantics as /spot/latest. Priced higher because one call returns the entire current price surface of the region.

NameTypeReqDescription
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1

No output schema declared.

No examples provided.

status ~56

Free. 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

term ~171

Paid (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 each term's price divided by GPUs per node, with lo/hi across regions and the discount to on-demand. Answers "what does a committed H100 cost against spot and on-demand, per cloud". Neo-cloud commitment prices are quote-only and excluded.

NameTypeReqDescription
gpustringyesNormalized GPU model with a hyperscaler mapping, e.g. `H100 SXM`, `A100 SXM 80GB`, `L4`, `T4`. Example: H100 SXM

No output schema declared.

No examples provided.

term_instance ~273

Paid (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 reserved/reservation terms as effective hourly with upfront amortized. `discount_pct` is relative to on-demand. AWS carries four reserved terms (1y/3y × no/all upfront), Azure two (1y/3y all upfront), GCP two resource-based committed-use terms (`cud_1y`, `cud_3y`, no upfront).

NameTypeReqDescription
instancestringyesInstance / machine / SKU type name exactly as listed by /instances (for example `c5.large`, `n2-standard-4`, `D2s_v5`). Example: c5.large
providerstringyesCloud provider. One of `aws`, `gcp`, `azure`.
regionstringyesRegion slug as listed by /catalog (for example `us-east-1` for AWS, `us-central1` for GCP, `us-east` for Azure). Azure slugs map to `eastus`, `westus2`, `westeurope`. Example: us-east-1

No output schema declared.

No examples provided.

tokens_board ~49

Paid (0.10 USDC per call). Every model's input, output and blended fixing for one day, plus the frontier basket.

NameTypeReqDescription
daystring–YYYY-MM-DD; default latest.

No output schema declared.

No examples provided.

tokens_fixing ~168

Paid (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 million tokens; `.BLEND` is (3·input + output) / 4. `CX.TOK.FRONTIER.<side>` is the median across the frontier basket listed by /tokens/models.

NameTypeReqDescription
daystring–YYYY-MM-DD; default latest.
tickerstringyesCX.TOK.<MODELCODE>.IN | OUT | BLEND, or CX.TOK.FRONTIER.<side>. Example: CX.TOK.FRONTIER.BLEND

No output schema declared.

No examples provided.

tokens_history ~78

Paid (0.05 USDC per call). Daily fixings for a token ticker, from the first snapshot (2026-09-14).

NameTypeReqDescription
fromstring–YYYY-MM-DD.
tickerstringyesToken ticker. Example: CX.TOK.FRONTIER.BLEND
tostring–YYYY-MM-DD.

No output schema declared.

No examples provided.

tokens_models ~90

Free. 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 min/max input and output price seen today. Also lists the frontier basket.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tokens_quotes ~134

Paid (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, DeepInfra, …), the LiteLLM price table and DeepInfra. Includes cache-read price and context length where known; variants such as batch tiers are marked in `extra.variant`.

NameTypeReqDescription
daystring–YYYY-MM-DD; default latest.
modelstringyesCanonical model slug from /tokens/models. Example: deepseek-v3

No output schema declared.

No examples provided.

Common questions

What is the corpusAI Cloud Pricing MCP server?

corpusAI Cloud Pricing is an MCP server listed in the public MCP registry as io.github.JTraversa/corpus-cloud-pricing-mcp. Cloud spot, on-demand, reserved and GPU rental prices with index fixings, paid per call over x402. This page covers its hosted endpoint (https://cloud.trycorpus.ai/mcp).

Is the corpusAI Cloud Pricing MCP server safe to use?

corpusAI Cloud Pricing scores 70 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 corpusAI Cloud Pricing MCP server expose?

corpusAI Cloud Pricing exposes 34 tools: health, catalog, instances, spot_events, spot_hourly, and 29 more. Their descriptions and schemas cost roughly 5,678 tokens of context every time the server is loaded.

Does the corpusAI Cloud Pricing MCP server require authentication?

No. We connected to corpusAI Cloud Pricing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the corpusAI Cloud Pricing MCP server still maintained?

corpusAI Cloud Pricing is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.