QVeris MCP server

Which servers in the official MCP registry are QVeris's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-09

← Back to QVeris

Whose server it is

Registry nameio.github.QVerisAI/mcppublished by QVerisAI on GitHub

Published under the GitHub organisation QVerisAI, the same one qveris.ai links from its homepage. The registry ties that namespace to a GitHub sign-in.

When we asked itchecked 2026-10-09

Staterequires sign-inchecked 2026-10-09

On 2026-10-09 the server answered and asked for a sign-in with a QVeris account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "qveris": {
      "type": "http",
      "url": "https://mcp.qveris.ai/mcp"
    }
  }
}

The first time it connects, the client opens a QVeris sign-in.

Also shipped through: npm

OpenAPI spec

32 paths, read 2026-10-09. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.