verifyax/verifyax-mcp

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**:
| Client | Setup reference |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------- |
| OpenAI ChatGPT | Connectors / MCP guide |
| Claude (Claude.ai, Code, Desktop) | Claude MCP docs |
| Cursor | Cursor MCP docs |
| Visual Studio Code (GitHub Copilot) | VS Code MCP docs |
| GitHub Copilot CLI | About Copilot CLI |
| Google Gemini CLI | Gemini CLI MCP docs |
| Amazon Quick Suite | MCP integration guide |
Any client that can connect via mcp-remote can also
use the hosted endpoint at https://mcp.verifyax.com/mcp.
> [!IMPORTANT]
> **Claude.ai custom connectors: use _No sign-in_ and an Authorization header.** This server
> authenticates with a VerifyAX API key, not OAuth, so in **Settings → Connectors → Add custom
> connector**:
>
> 1. URL: https://mcp.verifyax.com/mcp
> 2. Authentication: **No sign-in** — described in the dialog as "for servers that use an API key
> instead of OAuth". Leave _Sign in now_ unselected; this server publishes no OAuth metadata, so
> an OAuth attempt fails.
> 3. Under **Request headers**, add Authorization with the value Bearer sk-ver-api-....
>
> All 17 tools then appear, and Claude.ai lets you set approval per tool (it groups them as 12
> read-only and 5 write/delete — worth setting the write/delete group to require approval, since
> generate_scenario and evaluate_agent spend credits).
>
> Requires server **0.3.5 or later**: earlier builds matched the Bearer scheme case-sensitively
> and rejected clients that normalise it, which surfaced only as "Couldn't connect to the server."
> The X-VerifyAX-API-Key header works with the server but Claude.ai's header field rejects that
> name, so use Authorization.
> [!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
Seventeen tools mapped to user intents. Blocking tools poll internally and return only when work
completes (typically 30s–5min).
| Area | Tools | Blocking |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------: |
| **Agents** | register_agent · list_agents · delete_agent | — |
| **Scenarios** | list_compatible_tags · recommend_scenario_tags · search_scenario_tags · generate_scenario · list_scenarios · get_scenario · delete_scenario | **yes** (generate_scenario) |