mcpbeat

VerifyAX MCP Server

io.github.verifyax/mcp-server
answering

VerifyAX is answering right now. Last checked 11 min ago. 342 installs a week from npm. Last commit 28 Jul 2026.

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

Installs per day peak 265 · avg 25 · +426% w/w
a month agotoday
Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
127 ms
Response time
average over 24h
342
Installs / week
npm and PyPI

Connect this server

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

run in your terminal
claude mcp add mcp-server --transport http https://mcp.verifyax.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "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
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.verifyax.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.verifyax.com/mcp streamable-http needs key 130 ms 11 min ago

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 127 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 with the file path 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 key or an OAuth login: 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 127 ms on average, which is faster than 78% 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 342 times in the last week. Week over week that is +426%. 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?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.