mcpbeat Sign in

VerifyAX MCP Server

answering

VerifyAX is answering right now. Last checked 4 min ago. 80 installs a week from npm. Last commit 31 Oct 2026.

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

Installs per day peak 39 · avg 11 · +122% w/w
a month agotoday
Uptime history 91 days of history · worst day 96%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
131 ms
Response time
average over 24h
80
Installs / week
npm and PyPI

What the code does

We read the source, 2 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Secret passed into the image build Dockerfile:30
# Provide a dummy API key so the server starts for Glama's introspection checks.
# Users will provide their own VERIFYAX_API_KEY when running the server.
ENV VERIFYAX_API_KEY=dummy-key-for-introspection

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add mcp-server --transport http https://mcp.verifyax.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.verifyax.com/mcp
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://mcp.verifyax.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.verifyax.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp-server": {
      "type": "http",
      "url": "https://mcp.verifyax.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://mcp.verifyax.com/mcp streamable-http needs auth 167 ms 4 min ago

Alternatives to VerifyAX

same job, measured the same way
Agent Resolve MCP
by agent-resolve

Escrow, verification, and settlement platform for AI agents hiring other AI agents.

7 tools answering
Okareo
by okareo

Simulation, evaluation and monitoring for voice agents.

answering
G
Glint Model Hub — image generation for AI agents
by zzzjy765

Generate and edit images with every image model on the platform. Returns the image to the agent.

local only
passmcp
by sebastienrousseau

Evaluate an MCP server with passmcp and verify its attestations, from inside the agent. Read-only.

local only
operant-mcp
by saagpatel

Read-only MCP server for the OPERANT AI operating-agent calibration benchmark.

37 installs/wk 5 tools answering
Toolroute
by grossiweb

Route AI agent tasks to the best MCP server and LLM, scored on 132+ real benchmark executions.

3 177 installs/wk local only
scout
by sebastienrousseau

Evaluate an MCP server with scout and verify scout attestations, from inside the agent. Read-only.

local only
Magicweave Fastmcp
by fortunecasablancas

Author, validate, simulate, and one-click-build game economies on the Magicweave platform.

answering

VerifyAX — questions

Answers built from our own checks of this server.

Why is there no tool list for VerifyAX?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is VerifyAX working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 131 ms. The bar chart above shows every period we have measured.
How do I connect VerifyAX?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does VerifyAX need an API key?
Yes. Every time we knock, VerifyAX answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is VerifyAX?
It answers our handshake in 131 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use VerifyAX?
The npm package @verifyax/mcp-server was installed 80 times in the last week. Week over week that is +122%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is VerifyAX open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.verifyax.com, which runs on its operator's own terms.