INDIVIDUAL MCP TOOL

connections.catalog

Inspect all connector definitions and exact installed setup paths.

evalgate.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://www.evalgate.com/api/mcp

No auth detected

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

{}

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.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.evalgate]
url = "https://www.evalgate.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "evalgate": {
      "type": "http",
      "url": "https://www.evalgate.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: evalgate
Remote MCP URL: https://www.evalgate.com/api/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": {
    "evalgate": {
      "url": "https://www.evalgate.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "evalgate": {
      "type": "http",
      "url": "https://www.evalgate.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "evalgate",
  "transport": "streamable-http",
  "url": "https://www.evalgate.com/api/mcp"
}

MCP Inspector

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

project.inspect — Inspect the evaluations and project keys available in the authenticated organization.
project.plan — Return a non-mutating next-step plan for connecting a repository, evaluation, or trace source.
evaluations.list — List evaluations with a stable cursor for the organization.
runs.list — List evaluation runs with stable cursors and regression signals.
run.explain — Explain a run using its status, failed-case metadata, and evidence-lineage summary.
baseline.lineage — Show the published baseline anchor and its evidence lineage.
docs.search — Search the published OpenAPI operation catalog for relevant help.
connector.health — Show the latest connector-readiness reports for the organization.