VerifyAX MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

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.

# 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.

Connect this server

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

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

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

[mcp_servers.mcp-server]
url = "https://mcp.verifyax.com/mcp"

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

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

This one needs environment variables set before it will start: VERIFYAX_API_KEY (VerifyAX API key (Settings -> API Keys in the console). Sent to the gateway as Authorization: Bearer.), VERIFYAX_MCP_LOG_LEVEL (Log verbosity written to stderr: debug | info | warn | error | silent (default info).). The author declared them in the registry entry; get the values from the project itself.

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

Endpoints