Is the Jtraversa Corpus Cloud Pricing MCP server down?

mcp-registry/io.github.jtraversa/corpus-cloud-pricing-mcp · v1.0.0

As of 2026-10-17 10:36 UTC, the Jtraversa Corpus Cloud Pricing MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 14 minutes.

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

claude mcp add --transport http jtraversa-corpus-cloud-pricing-mcp-serve https://cloud.trycorpus.ai/mcp

{
  "mcpServers": {
    "jtraversa-corpus-cloud-pricing-mcp-serve": {
      "type": "http",
      "url": "https://cloud.trycorpus.ai/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (95/100)

What to fix (2)

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jtraversa/corpus-cloud-pricing-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jtraversa/corpus-cloud-pricing-mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~7,727 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.77% uptime over 30 days.

Largest tool definitions

• spot_events ~511 tokens
• spot_monthly ~435 tokens
• spot_daily ~408 tokens
• reserved ~377 tokens
• spot_hourly ~357 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jtraversa%2Fcorpus-cloud-pricing-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jtraversa%2Fcorpus-cloud-pricing-mcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.jtraversa%2Fcorpus-cloud-pricing-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jtraversa%2Fcorpus-cloud-pricing-mcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jtraversa%2Fcorpus-cloud-pricing-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jtraversa%2Fcorpus-cloud-pricing-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:90a171920c5ea9e4…, first seen 2026-10-17, included at leaf 9303 of 17,426. Version history · verify what your client received.

Tools (36)

• attestations
• azure_eviction
• capacity_board
• capacity_headline
• capacity_history
• capacity_stress
• catalog
• gpu_index
• gpu_models
• gpu_quotes
• gpu_snapshot
• health
• index_board
• index_fixing
• index_history
• index_tickers
• instances
• ondemand
• ondemand_snapshot
• reserved
• reserved_snapshot
• spot_daily
• spot_events
• spot_hourly
• spot_latest
• spot_monthly
• spot_snapshot
• status
• term
• term_curve
• term_instance
• tokens_board
• tokens_fixing
• tokens_history
• tokens_models
• tokens_quotes

Compare: most reliable other servers · most reliable data servers · most reliable devops servers · most reliable finance servers · most reliable ml servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Jtraversa Corpus Cloud Pricing MCP server down right now?

As of 2026-10-17 10:36 UTC, the Jtraversa Corpus Cloud Pricing MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 14 minutes.

How many tools does Jtraversa Corpus Cloud Pricing MCP server provide?

Jtraversa Corpus Cloud Pricing MCP server advertises 36 tools, including attestations, azure_eviction, capacity_board, capacity_headline, capacity_history.

How do I install Jtraversa Corpus Cloud Pricing MCP server?

Point your MCP client at this streamable-http endpoint: https://cloud.trycorpus.ai/mcp

Is the Jtraversa Corpus Cloud Pricing MCP server safe to connect to an AI agent?

Glimind scanned all 35 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Jtraversa Corpus Cloud Pricing MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.