VerifyAX

Name: VerifyAX
Author: verifyax

by verifyaxversion 0.4.0i★ –iComputer or cloud

Registry nameio.github.verifyax/mcp-server

Install

Overview

Description from the maker (original English)

Evaluate, benchmark, and simulate AI agents on the VerifyAX agent-evaluation platform.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: VERIFYAX_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: VERIFYAX_API_KEY, VERIFYAX_MCP_LOG_LEVEL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.verifyax.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "verifyax": {
      "command": "npx",
      "args": [
        "-y",
        "@verifyax/mcp-server"
      ],
      "env": {
        "VERIFYAX_API_KEY": "your-value",
        "VERIFYAX_MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http verifyax https://mcp.verifyax.com/mcp

Or run it on your computer

claude mcp add verifyax --env VERIFYAX_API_KEY=your-value --env VERIFYAX_MCP_LOG_LEVEL=your-value -- npx -y @verifyax/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "verifyax": {
      "url": "https://mcp.verifyax.com/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "verifyax": {
      "command": "npx",
      "args": [
        "-y",
        "@verifyax/mcp-server"
      ],
      "env": {
        "VERIFYAX_API_KEY": "your-value",
        "VERIFYAX_MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "verifyax": {
      "type": "http",
      "url": "https://mcp.verifyax.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "verifyax": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@verifyax/mcp-server"
      ],
      "env": {
        "VERIFYAX_API_KEY": "your-value",
        "VERIFYAX_MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.verifyax.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

VERIFYAX_API_KEY secret required env
VerifyAX API key (Settings -> API Keys in the console). Sent to the gateway as Authorization: Bearer.
VERIFYAX_MCP_LOG_LEVEL env
Log verbosity written to stderr: debug | info | warn | error | silent (default info).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account verifyax, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32497 servers in this category
Published to the registry more recently than 56% of the other 32497 servers in this category
Basic checks equal to or better than 100% of the other 32497 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is VerifyAX safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: VERIFYAX_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 31 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Zoo MCP

by KittyCAD

An MCP server that provides access to the Zoo API for various CAD operations and tools.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

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`)
Evaluation	`evaluate_agent` · `list_recent_runs` · `get_run_details` · `get_evaluation_report` · `get_run_output`	yes (`evaluate_agent`)
Usage	`get_usage_summary` · `preview_run_cost`	—

[!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

[!NOTE]

The version here is deliberately unpinned, so this command always fetches the current server.

Only the verifyax-mcp plugin pins an exact

version (@verifyax/mcp-server@ ), because a marketplace plugin promises that users

get a new server build only when the plugin version is bumped. Setting up by hand carries no such

promise, so tracking the latest release is the right default. Pin it yourself if you need

reproducibility: -p @verifyax/mcp-server@0.3.5.

-p … verifyax-mcp-server names the binary explicitly because the package ships two

(verifyax-mcp-server, verifyax-mcp-server-http) and neither matches the package name, so a

bare npx -y @verifyax/mcp-server fails with "could not determine executable to run".

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

Your MCP client connects to https://mcp.verifyax.com/mcp (remote HTTP) or spawns npx -p @verifyax/mcp-server verifyax-mcp-server (local stdio).
The client sends your Ver

Only the beginning is shown; read the rest in the repo

VerifyAX

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Zoo MCP

README from the maker

Contents

Supported clients

Supported tools

Before you start

Remote HTTP (hosted at mcp.verifyax.com)

Local stdio (verifyax-mcp-server via npx)

Install the MCP server

Remote HTTP (recommended)

Local stdio

How it works

Architecture and communication

Remote HTTP (hosted at `mcp.verifyax.com`)

Local stdio (`verifyax-mcp-server` via npx)