VerifyAX MCP Server

The official Model Context Protocol (MCP) server for VerifyAX: a cloud-hosted bridge that gives your AI tools secure, real-time access to register agents, generate scenarios, run simulations, and read evaluations on the VerifyAX platform.

Getting started · Supported tools · Security · Deploy your own · Report an issue

The official VerifyAX MCP Server is a bridge between your MCP-compatible AI client and the VerifyAX agent-evaluation platform. Once configured, it lets you register agents, generate scenarios, run simulations, and read evaluations in natural language — without writing API scripts.

With the VerifyAX MCP Server, you can:

• Register and test agents (A2A or API) and confirm connectivity before evaluation.
• Generate scenarios from skill tags and wait for completion in one tool call.
• Run evaluations and read scores, transcripts, and credit usage without manual polling.

It complements (does not replace) the verifyax-api skill: the skill is for developers writing code; the MCP server is for conversational workflows.

Contents

• Supported clients
• Supported tools
• Before you start
• Install the MCP server
• How it works
• Example workflows
• Tips and tricks
• Data and security
• Troubleshooting
• Support and feedback
• Disclaimer
• For developers
• License

Supported clients

The VerifyAX MCP Server works with MCP-compatible clients that support Streamable HTTP or stdio:

Any client that can connect via mcp-remote can also use the hosted endpoint at https://mcp.verifyax.com/mcp.

[!TIP] For step-by-step Claude setup and how this compares to the VerifyAX skill and SDK, see docs/using-verifyax-with-claude.md.

Supported tools

Twelve tools mapped to user intents. Blocking tools poll internally and return only when work completes (typically 30s–5min).

[!NOTE] For tool descriptions (what Claude reads to pick a tool) and rationale, see docs/tool-descriptions.md. Package-level reference: packages/mcp-server/README.md.

Before you start

Requirements depend on how you connect.

Remote HTTP (hosted at mcp.verifyax.com)

• A VerifyAX API key (Settings → API Keys in the console)
• An MCP client with Streamable HTTP support, or Node.js 18+ to run the mcp-remote proxy

Local stdio (verifyax-mcp-server via npx)

• Node.js ≥ 20
• A VerifyAX API key in your client config (VERIFYAX_API_KEY)

The npm package exposes two binaries (verifyax-mcp-server and verifyax-mcp-server-http); pass the stdio binary name explicitly when using npx.

Install the MCP server

Remote HTTP (recommended)

Hosted endpoint:

https://mcp.verifyax.com/mcp

Send your VerifyAX API key on the initialize request. The hosted server does not store keys — each client session brings its own.

Cursor (native URL — v0.48+):

{
  "mcpServers": {
    "verifyax": {
      "url": "https://mcp.verifyax.com/mcp",
      "headers": {
        "Authorization": "Bearer sk-ver-api-..."
      }
    }
  }
}

Do not add a transport field — Cursor detects Streamable HTTP from the URL. You can also use "X-VerifyAX-API-Key": "sk-ver-api-..." instead of Authorization.

Claude Desktop / clients without native HTTP (mcp-remote):

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "verifyax": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.verifyax.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${VERIFYAX_AUTH}"
      ],
      "env": {
        "VERIFYAX_AUTH": "Bearer sk-ver-api-..."
      }
    }
  }
}

Use --transport http-only because this server speaks Streamable HTTP only (no legacy SSE). You can also pass X-VerifyAX-API-Key: sk-ver-api-... via --header instead of Authorization.

Restart your MCP client after changing config.

Local stdio

Claude Code:

claude mcp add verifyax --env VERIFYAX_API_KEY=sk-ver-api-... -- npx -y -p @verifyax/mcp-server verifyax-mcp-server

Claude Desktop:

{
  "mcpServers": {
    "verifyax": {
      "command": "npx",
      "args": ["-y", "-p", "@verifyax/mcp-server", "verifyax-mcp-server"],
      "env": { "VERIFYAX_API_KEY": "sk-ver-api-..." }
    }
  }
}

Restart the client after changing config, then describe what you want in natural language.

How it works

Architecture and communication

1. Your MCP client connects to https://mcp.verifyax.com/mcp (remote HTTP) or spawns npx -p @verifyax/mcp-server verifyax-mcp-server (local stdio).
2. The client sends your VerifyAX API key on initialize (Authorization: Bearer … or X-VerifyAX-API-Key for HTTP; VERIFYAX_API_KEY env for stdio).
3. The server calls the VerifyAX API on your behalf. Blocking tools (generate_scenario, evaluate_agent) poll job status internally and return only when work finishes.

Permission and billing