com.verixid/verifierofficial
A
licenseNot graded
qualityC
maintenanceVerifies VerixID proof-of-existence records by Record ID and optionally proves ownership with an Ownership Key, without requiring the original file.
MIT
VerixID Verifier
by com.verixid
Server Details
Verify VerixID proof-of-existence records and optionally prove ownership.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
A4.8/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no possibility of confusing it with another. The tool's purpose is clearly and uniquely defined in its description.
Naming Consistency5/5
With a single tool, naming consistency is trivially perfect. The name 'verixid_verify' is descriptive and follows a consistent format.
Tool Count5/5
The server has a very narrow purpose—verifying VerixID records. One tool is perfectly scoped for this domain and no additional tools are needed.
Completeness5/5
The single tool covers the complete verification workflow: existence check, ownership verification, and next-step guidance. There are no obvious gaps for the stated purpose.
Available Tools
1 toolverixid_verifyAInspect
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).
Inputs: record_id (required), ownership_key.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Privacy-first document verification anchored to the public ledger.
Verify Attest agreements, stamp codes, receipts, proofs and SHA-256 fingerprints, with no sign-in.
Read-only verifier for 25 ProofRelay MCP tools and non-confidential evidence bundles.
Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to verify document timestamps and list all recorded proofs on the Verus blockchain using a VerusID. It queries public Verus RPC endpoints to facilitate hash verification without requiring API keys or authentication.347 npmMIT
- AlicenseNot gradedqualityBmaintenanceVerifies bernstein run receipts and hash chains by recomputing embedded chains, checking signatures, and returning signed verdicts.Apache 2.0
- FlicenseAqualityBmaintenanceEnables agents to verify claims against a real falsification ledger, querying pre-registered refutation thresholds, recorded verdicts, and verifier drift metrics instead of guessing.5-
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.