Verifyax MCP Server

VerifyAX MCP

Conversational access to the VerifyAX agent-evaluation platform, plus the typed SDK it is built on. Two packages in one pnpm monorepo:

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

Install the MCP server

Requires Node ≥ 20 and a VerifyAX API key (Settings → API Keys in the console).

Claude Code:

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

Claude Desktop (claude_desktop_config.json):

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

Restart the client, then describe what you want. See packages/mcp-server for the full tool list and configuration.

What you can ask

Once installed, just describe the task — Claude picks the tool:

• “List the skill tags I can use for an interview scenario on VerifyAX.”
• “Register the A2A agent at https://my-agent.example.com and run a quick interview eval.”
• “Generate an info_exchange scenario tagged empathy and coordination, then show me the scores.”
• “What did my last 5 simulation runs cost?”

Blocking tools (generate_scenario, evaluate_agent) poll internally and return only when the work completes (typically 30s–5min) — no manual status checks.

Troubleshooting

• “VERIFYAX_API_KEY is not set” — the key isn’t reaching the server. Check the env block in your MCP client config.
• Authentication failed — the key is invalid, revoked, or from the wrong environment. Mint a fresh one in the console.
• Tool calls don’t appear — MCP clients load tools at startup; restart the client (or start a new session) after adding the server.
• Want logs? Set VERIFYAX_MCP_LOG_LEVEL=debug. Logs are structured JSON on stderr; stdout is reserved for the MCP protocol.

Status

See docs/PLAN.md for the phased execution plan and CLAUDE.md for project context and architecture decisions.

This project is maintained internally by the VerifyAX team at Conscium. External pull requests aren't accepted — please open an issue to report a bug, an outdated API behavior, or a feature request; that's the best way to reach us. CONTRIBUTING.md is the development reference for maintainers and forks.

Development

Requires Node ≥ 20 and pnpm 10.

pnpm install      # install workspace dependencies
pnpm build        # build all packages (topological order)
pnpm test         # run unit tests
pnpm lint         # lint
pnpm format       # format with prettier

Network-dependent suites: pnpm test:integration (live API, needs VERIFYAX_TEST_KEY) and pnpm test:conformance (spawns the built MCP server over stdio).

Debugging with MCP Inspector

MCP Inspector is the official interactive UI for listing tools, calling them, and inspecting responses. Run it with npx — no install required.

Shells: the commands below use \ line-continuations (bash / zsh / macOS / Linux). In Windows PowerShell, put each command on one line, or continue with a backtick ` instead of \.

Pass the key with -e: Inspector does not inherit your shell environment — the spawned server only sees variables passed explicitly via -e KEY=value.

stdio (local default) — Inspector spawns the server as a subprocess. Build first, then:

pnpm build

npx @modelcontextprotocol/inspector \
  -e VERIFYAX_API_KEY=sk-ver-api-... \
  node packages/mcp-server/dist/index.js

# Windows PowerShell (single line)
pnpm build
npx @modelcontextprotocol/inspector -e VERIFYAX_API_KEY=sk-ver-api-... node packages/mcp-server/dist/index.js

Inspector opens a browser tab (default http://localhost:6274). Use the Tools pane to call list_compatible_tags or other non-blocking tools first.

To exercise the published package without a local build:

npx @modelcontextprotocol/inspector \
  -e VERIFYAX_API_KEY=sk-ver-api-... \
  npx -y @verifyax/mcp-server

Windows — avoid spaces in the Command path. Inspector's stdio launcher splits the spawn command on spaces, so a node path like C:\Program Files\nodejs\node.exe (or a repo under a folder such as OneDrive - Company) fails with "command not found" / "connection closed". Use space-free paths: the 8.3 short name for node (C:\PROGRA~1\nodejs\node.exe) and a no-space working copy (e.g. a directory junction: mklink /J C:\verifyax "C:\Users\you\OneDrive - Co\verifyax"). Or skip the subprocess entirely and use the Streamable HTTP mode below, which has no spawn step and isn't affected.

Streamable HTTP — for the HTTP entry point (verifyax-mcp-server-http). Works the same on all platforms (no command spawn, so the spaces caveat above doesn't apply). Start the server in one terminal, then open Inspector in another:

# terminal 1
pnpm build
node packages/mcp-server/dist/http.js

# terminal 2
npx @modelcontextprotocol/inspector

In the Inspector UI, choose Streamable HTTP, set the URL to http://127.0.0.1:8080/mcp, and add a header: Authorization: Bearer sk-ver-api-... (or X-VerifyAX-API-Key: sk-ver-api-...).

For scripted checks from the CLI:

npx @modelcontextprotocol/inspector --cli http://127.0.0.1:8080/mcp \
  --transport http \
  --header "Authorization: Bearer sk-ver-api-..." \
  --method tools/list

Set VERIFYAX_MCP_LOG_LEVEL=debug on the server process to see structured JSON logs on stderr while you test.

Privacy

The MCP server sends no telemetry. It talks only to the VerifyAX API using the key you provide via VERIFYAX_API_KEY.

License

Apache-2.0. See LICENSE.