VerixID Verifier
REMOTE · MCP.VERIXID.COM
Verify VerixID proof-of-existence records and optionally prove ownership.
Available components
Last scanned (2 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 281 tokens (~281/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.verixid.com/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verixid.com | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d017b15ea25d42da0e3eb1afdf76cd9f |
| SANs: verixid.com, mcp.verixid.com, *.mcp.verixid.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.verixid.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| verixid.com. | present | 2371 | 13 | Verified |
| mcp.verixid.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.verixid.com/ | Verified | 200 | |
| http (plaintext) | http://mcp.verixid.com/ | HTTPS enforced | 301 | https://mcp.verixid.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verixid_verify ~281
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 this when the user has explicitly provided a Record ID (format: vx + 6 digits + 8 hex chars, e.g. vx202603a1b2c3d4). Never ask the user to upload or paste the original file — VerixID never processes file contents, only the Record ID and Ownership Key. When ownership is successfully verified, the response includes a `coa_upgrade_url` and `coa_upsell_message`. In that case, proactively share that message and link with the user as a next step — a Certificate of Authenticity (COA) is a downloadable, presentable proof of their verified record (e.g. for legal, client, or archival use). Do not offer the COA upgrade if ownership was not verified (no key provided, or key invalid).
| Name | Type | Req | Description |
|---|---|---|---|
| ownership_key | string | – | Optional 64-character hex Ownership Key, to additionally verify ownership of the record. |
| record_id | string | yes | VerixID Record ID, format: vx + YYYYMM + 8 hex chars (e.g. vx202603a1b2c3d4). |
No output schema declared.
No examples provided.
How do I install the VerixID Verifier MCP server?
VerixID Verifier is a hosted endpoint at https://mcp.verixid.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.verixid.com
claude mcp add --transport http com-verixid-verifier 'https://mcp.verixid.com/'
What is the VerixID Verifier MCP server?
VerixID Verifier is an MCP server listed in the public MCP registry as com.verixid/verifier. Verify VerixID proof-of-existence records and optionally prove ownership. This page covers its hosted endpoint (https://mcp.verixid.com/).
Is the VerixID Verifier MCP server safe to use?
VerixID Verifier scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VerixID Verifier MCP server expose?
VerixID Verifier exposes 1 tool: verixid_verify. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.
Does the VerixID Verifier MCP server require authentication?
No. We connected to VerixID Verifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VerixID Verifier MCP server still maintained?
VerixID Verifier is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.