General Tools
trycorpus.ai
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://cloud.trycorpus.ai/mcp
MCP server metadata
- Name
- corpus-cloud-pricing
- Version
- 1.0.0
corpusAI Cloud Pricing: cloud spot, on-demand and reserved prices for AWS, GCP and Azure, from price-change events per zone to monthly history back to 2014; GPU rental quotes from neo-clouds and marketplaces with daily index fixings (tickers CX.<MODEL>.<SEGMENT>); LLM token prices; term structure; capacity stress. Call the free tools (catalog, gpu_models, index_tickers, tokens_models, status) first to learn exact names. Paid tools cost 0.01 to 0.10 USDC per call and are charged to the prepaid key sent as "Authorization: Bearer ck_…"; without a key they return the price and how to pay. Docs: https://cloud.trycorpus.ai/docs
Known tools 34
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.corpus-cloud-pricing]
url = "https://cloud.trycorpus.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"corpus-cloud-pricing": {
"type": "http",
"url": "https://cloud.trycorpus.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: corpus-cloud-pricing
Remote MCP URL: https://cloud.trycorpus.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"corpus-cloud-pricing": {
"url": "https://cloud.trycorpus.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"corpus-cloud-pricing": {
"type": "http",
"url": "https://cloud.trycorpus.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "corpus-cloud-pricing",
"transport": "streamable-http",
"url": "https://cloud.trycorpus.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.