← rauta.ai

INDIVIDUAL MCP TOOL

identify_rauta

Identify this Rauta MCP backend before diagnosing auth or scope errors.

rauta.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://gateway.rauta.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for identify_rauta and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

rauta.ai

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.rauta-gateway]
url = "https://gateway.rauta.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "rauta-gateway": {
      "type": "http",
      "url": "https://gateway.rauta.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: rauta-gateway
Remote MCP URL: https://gateway.rauta.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": {
    "rauta-gateway": {
      "url": "https://gateway.rauta.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "rauta-gateway": {
      "type": "http",
      "url": "https://gateway.rauta.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "rauta-gateway",
  "transport": "streamable-http",
  "url": "https://gateway.rauta.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • signup — Start creating a Rauta gateway account.
  • verify_signup — STEP 2 OF 2: complete signup with the 6-digit code the user received by email.
  • list_gpus — List GPU types currently available across providers, with per-provider price, region, and availability.
  • lookup_model — Look up a Hugging Face model: parameter count, context window, VRAM needed at fp16/int8/int4, and which market GPUs can fit it.
  • recommend_workload — Recommend the best provider+GPU for a workload.
  • leaderboard — Inference leaderboard for one category: 'cloud' (GPU rental providers), 'hardware' (raw GPU types), or 'inference' (serverless inference APIs).
  • cold_start_stats — Real provisioning (cold-start) latency AND supply health per provider+GPU: p50/p95/min provision time, success/error counts, failure rate, and — for every failing bucket — the actionable cause.
  • compare_providers — Cross-provider time series of TTFT p50/p95, latency, tokens/sec and availability.