VerixID Verifier
Verify VerixID proof-of-existence records and optionally prove ownership.
我該用這個嗎
品質與安全性
根據工具定義與協定合規性的自動化分析。
上下文成本
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高，可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案：
{
"mcpServers": {
"verifier": {
"url": "https://mcp.verixid.com/"
}
}
}遠端端點
https://mcp.verixid.com/streamable-http它能做什麼
工具清單
工具（1）
🟡verixid_verify(record_id, ownership_key)
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).
輸入結構描述
{
"type": "object",
"properties": {
"record_id": {
"type": "string",
"description": "VerixID Record ID, format: vx + YYYYMM + 8 hex chars (e.g. vx202603a1b2c3d4)."
},
"ownership_key": {
"description": "Optional 64-character hex Ownership Key, to additionally verify ownership of the record.",
"type": "string"
}
},
"required": [
"record_id"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}社群
證據