Skip to content
VerixID logo

VerixID MCP server

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

read 2026-10-21

← Back to VerixID

Whose server it is
  • Registry namecom.verixid/verifierverified in the MCP registry

The registry name sits under verixid.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools1
  • Server calls itselfVerixID Verifier
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 314 ms.

Should an agent connect itConnect it, with care
  • Its tools do verify a shared record ID independently, but not register a timestamped fingerprint of a digital file; add file registration to backend workflows through an API.

Once connected

  • For "verify a shared record ID independently", the likely first call is verixid_verify.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 15, the first on 2026-10-21
  • INITE MCP score78 of 100answers 100 · does the job 33 · definitions 83 · context 100 · connects 100
  • What an agent can do with it1 of 3 use cases
  • Answered100% of days15 of 15 daily checks
  • Median first answer271 ms
  • Space in an agent's context≈ 337 tokensthe definitions of all its tools (1), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 1 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 1 of 1

What an agent can do with it

  • cannot · register a timestamped fingerprint of a digital file
  • can do · verify a shared record ID independently
  • cannot · add file registration to backend workflows through an API

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers1 tools · read 2026-10-21
  • verixid_verify

    Verify a VerixID registration record using a Record ID, optionally with an Ownership Key. Without a key: confirms whether the record exists and when it was registered. With a key: additionally proves ownership of the record. Only call…

How to connect

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

{
  "mcpServers": {
    "verifier": {
      "type": "http",
      "url": "https://mcp.verixid.com/"
    }
  }
}

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.verixid.com/ as a custom connector in the settings.

OpenAPI spec

2 paths, read 2026-10-21. 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.