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

NPM · CORPUS-CLOUD-PRICING-MCP · 2 COMPONENTS · SCANNED SEP 27

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

63 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1923 tokens (~68/item across 28 items; 28 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% 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 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 29 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the corpusAI Cloud Pricing MCP server?

corpusAI Cloud Pricing runs locally as an npm package, launched with npx -y corpus-cloud-pricing-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · corpus-cloud-pricing-mcp

# add to Claude Code
claude mcp add jtraversa-corpus-cloud-pricing-mcp -- npx -y corpus-cloud-pricing-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "corpus-cloud-pricing-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "corpus-cloud-pricing-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add jtraversa-corpus-cloud-pricing-mcp -- npx -y corpus-cloud-pricing-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "corpus-cloud-pricing-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jtraversa-corpus-cloud-pricing-mcp --command npx --arg -y --arg corpus-cloud-pricing-mcp
# ~/.hermes/config.yaml
mcp_servers:
  jtraversa-corpus-cloud-pricing-mcp:
    command: "npx"
    args: ["-y", "corpus-cloud-pricing-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "corpus-cloud-pricing-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add jtraversa-corpus-cloud-pricing-mcp -t stdio -c npx -a -y corpus-cloud-pricing-mcp
// mcp.json
{
  "mcpServers": {
    "jtraversa-corpus-cloud-pricing-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "corpus-cloud-pricing-mcp"
      ]
    }
  }
}
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.

  • 26 Sept 26 63

    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 · Analysed npm/corpus-cloud-pricing-mcp@0.1.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 114 packages
Packages resolved 114
Stale 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 28 exposed · ~1,817 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
capacity_board ~38

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

NameTypeReqDescription
daystring––

No output schema declared.

No examples provided.

capacity_history ~46

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

NameTypeReqDescription
fromstring––
gpustringyes–
tostring––

No output schema declared.

No examples provided.

capacity_stress ~69

Paid (0.01 USDC). Capacity stress score for one GPU model on one day, 0 slack … 100 tight, with every component (availability, io.net units, Vast supply, spot-to-on-demand ratio).

NameTypeReqDescription
daystring––
gpustringyes–

No output schema declared.

No examples provided.

catalog ~29

Free. Providers, region slugs, coverage windows, prices per call and the source legend. Call first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gpu_index ~65

Paid (0.05 USDC). Daily lo/median/mean/hi per provider and market for one GPU model, with aws-spot and gcp-spot legs.

NameTypeReqDescription
fromstring––
gpustringyes–
tostring––

No output schema declared.

No examples provided.

gpu_models ~21

Free. Normalised GPU model names with quote counts and providers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gpu_quotes ~69

Paid (0.01 USDC). Latest GPU rental quotes for one model across neo-clouds and marketplaces, USD per GPU-hour.

NameTypeReqDescription
gpustringyesModel from gpu_models, e.g. "H100 SXM"
marketstring––
providerstring––

No output schema declared.

No examples provided.

index_board ~31

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

NameTypeReqDescription
daystring––

No output schema declared.

No examples provided.

index_fixing ~63

Paid (0.01 USDC). One day's index fixing for a ticker such as CX.H100SXM.NEO (median USD per GPU-hour, lo, hi, n).

NameTypeReqDescription
daystring–YYYY-MM-DD
tickerstringyes–

No output schema declared.

No examples provided.

index_history ~55

Paid (0.05 USDC). Daily fixings for a ticker; SPOT tickers reach back to 2022.

NameTypeReqDescription
fromstring––
tickerstringyes–
tostring––

No output schema declared.

No examples provided.

index_tickers ~31

Free. Every index ticker (CX.<MODEL>.<SEGMENT>) with segment definitions and the methodology version.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

instances ~73

Free. Instance types available in a region with coverage dates.

NameTypeReqDescription
prefixstring–Type-name prefix filter, e.g. c5.
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)

No output schema declared.

No examples provided.

ondemand ~87

Paid (0.01 USDC). On-demand list-price change history of one instance type.

NameTypeReqDescription
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)

No output schema declared.

No examples provided.

reserved ~92

Paid (0.01 USDC). AWS reserved-instance effective hourly price history (1y/3y, no/all upfront).

NameTypeReqDescription
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)
ri_typestring––

No output schema declared.

No examples provided.

spot_daily ~121

Paid (0.05 USDC). Full daily spot price history of one instance type, all eras, source per row.

NameTypeReqDescription
fromstring–Start, ISO 8601 UTC
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)
tostring–End, ISO 8601 UTC

No output schema declared.

No examples provided.

spot_events ~125

Paid (0.01 USDC). Raw spot price-change events for one instance type with zone and timestamp.

NameTypeReqDescription
fromstring–Start, ISO 8601 UTC
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
limitinteger––
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)
tostring–End, ISO 8601 UTC

No output schema declared.

No examples provided.

spot_hourly ~119

Paid (0.01 USDC). Hourly time-weighted OHLC spot bars for one instance type.

NameTypeReqDescription
fromstring–Start, ISO 8601 UTC
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)
tostring–End, ISO 8601 UTC

No output schema declared.

No examples provided.

spot_latest ~86

Paid (0.01 USDC). Current spot price per zone for one instance type.

NameTypeReqDescription
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)

No output schema declared.

No examples provided.

spot_monthly ~90

Paid (0.05 USDC). Monthly spot history back to 2014 for legacy AWS types.

NameTypeReqDescription
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)

No output schema declared.

No examples provided.

spot_snapshot ~65

Paid (0.10 USDC). Current spot price of every type and zone in a region.

NameTypeReqDescription
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)

No output schema declared.

No examples provided.

status ~16

Free. Freshness of every data source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

term_curve ~72

Paid (0.05 USDC). Term structure per hyperscaler for one GPU model, USD per GPU-hour: spot, on-demand, 1y, 3y with discounts.

NameTypeReqDescription
gpustringyesModel with a hyperscaler mapping, e.g. "H100 SXM", "T4"

No output schema declared.

No examples provided.

term_instance ~102

Paid (0.01 USDC). Price ladder for one instance type: spot, on-demand, 1-year and 3-year commitments with discount to on-demand.

NameTypeReqDescription
instancestringyesInstance type exactly as listed by the instances tool (e.g. c5.large)
providerstringyesCloud provider
regionstringyesRegion slug from the catalog tool (e.g. us-east-1, us-central1, us-east)

No output schema declared.

No examples provided.

tokens_board ~40

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

NameTypeReqDescription
daystring––

No output schema declared.

No examples provided.

tokens_fixing ~62

Paid (0.01 USDC). One day's token price fixing for CX.TOK.<MODEL>.IN, .OUT or .BLEND, or CX.TOK.FRONTIER.<side>.

NameTypeReqDescription
daystring––
tickerstringyes–

No output schema declared.

No examples provided.

tokens_history ~45

Paid (0.05 USDC). Daily fixings for a token ticker.

NameTypeReqDescription
fromstring––
tickerstringyes–
tostring––

No output schema declared.

No examples provided.

tokens_models ~38

Free. Every LLM with a token price fixing: canonical slug, ticker codes, sources, hosts and today's price range, plus the frontier basket.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tokens_quotes ~67

Paid (0.01 USDC). Every source and host's price for one model on one day, USD per million input/output tokens.

NameTypeReqDescription
daystring––
modelstringyesCanonical slug from tokens_models, e.g. "claude-sonnet-5"

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 npm package (corpus-cloud-pricing-mcp).

Is the corpusAI Cloud Pricing MCP server safe to use?

corpusAI Cloud Pricing scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. 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 28 tools: catalog, instances, gpu_models, index_tickers, status, and 23 more. Their descriptions and schemas cost roughly 1,817 tokens of context every time the server is loaded.

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.

What licence is the corpusAI Cloud Pricing MCP server under?

corpusAI Cloud Pricing declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.