INDIVIDUAL MCP TOOL

list_models

What the gateway can route right now: the modality x lane capability matrix (which modalities are served on cloud, self-hosted, container, native, rented lanes) plus the live model list with capability, context window and daily quota.

aivoicecall.netnone authenticationAvailability not checked

LIVE ENDPOINT

https://aigateway.aivoicecall.net/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_models 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

aivoicecall.net

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.aigateway]
url = "https://aigateway.aivoicecall.net/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "aigateway": {
      "type": "http",
      "url": "https://aigateway.aivoicecall.net/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: aigateway
Remote MCP URL: https://aigateway.aivoicecall.net/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": {
    "aigateway": {
      "url": "https://aigateway.aivoicecall.net/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "aigateway": {
      "type": "http",
      "url": "https://aigateway.aivoicecall.net/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "aigateway",
  "transport": "streamable-http",
  "url": "https://aigateway.aivoicecall.net/mcp"
}

MCP Inspector

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

Related tools

cost_report — Aggregate traffic (request counts, average latency, success rate) and the headline savings: what the same tokens would have cost on one paid provider versus what they actually cost across the gateway's lanes.
failover_state — Every provider's current health and routing priority, highest-priority first — the live failover posture.
health_history — Uptime (fraction of probes healthy) and average latency per provider over a recent window, with a downsampled tail of probe points.