VerixID Verifier
REMOTE · MCP.VERIXID.COM · SCANNED AUG 20
Verify VerixID proof-of-existence records and optionally prove ownership.
Available components
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 →
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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.verixid.com
claude mcp add --transport http com-verixid-verifier https://mcp.verixid.com/
[mcp_servers.com-verixid-verifier] url = "https://mcp.verixid.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-verixid-verifier": {
"type": "remote",
"url": "https://mcp.verixid.com/",
"enabled": true
}
}
} openclaw mcp add com-verixid-verifier --url https://mcp.verixid.com/ --transport streamable-http
mcp_servers:
com-verixid-verifier:
url: "https://mcp.verixid.com/" {
"mcpServers": {
"com-verixid-verifier": {
"type": "http",
"url": "https://mcp.verixid.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Aug 26 64
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 20 Aug 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 | 19 Jul 2026 | 17 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 899b30175893cd610ef21a3cbb8a973f |
| 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 |
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 |
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.
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.