# VERIXID MCP SERVER DOCUMENTATION

Official documentation for the VerixID Model Context Protocol (MCP) Server integration. This server enables AI agents (Claude, ChatGPT, Cursor, etc.) to perform programmatic digital proof verification directly within conversational interfaces without browser-based interaction.

---

## CONNECTION & REGISTRY SPECIFICATIONS

| Parameter | Specification |
| :--- | :--- |
| **Base Endpoint** | `https://mcp.verixid.com/` |
| **Transport Protocol** | Streamable HTTP |
| **Authentication** | Public (No API key required; rate-limited) |
| **Discovery URI** | `https://mcp.verixid.com/.well-known/mcp.json` (SEP-1649) |
| **Registry ID** | `com.verixid/verifier` (Version 1.0.0) |

---

## TOOL SPECIFICATION: `verixid_verify`

Evaluates a single VerixID ledger entry using a `record_id` and an optional `ownership_key`.

### Input Parameters
| Parameter | Type | Required | Format / Validation Rules |
| :--- | :--- | :--- | :--- |
| `record_id` | String | Yes | Format: `vx` + `YYYYMM` + 8 hexadecimal characters (e.g., `vx202607c8835992`). |
| `ownership_key` | String | No | 64-character hexadecimal string. Used for private ownership verification. |

### Response Schema Behavior
* **Without `ownership_key`:** Returns record existence status, registration timestamp, and a truncated hash preview (`hash_preview`). `ownership_verified` resolves to `false`.
* **With Valid `ownership_key`:** Resolves `ownership_verified: true`, returns an Ed25519 signature, and provides a COA upgrade payload (if eligible).
* **With Invalid `ownership_key`:** Resolves `ownership_verified: false` without exposing confidential record details.

---

## INPUT & OUTPUT EXAMPLES

### 1. Public Verification (Without Key)
**JSON Request:**
```json
{
  "record_id": "vx202607c8835992",
  "registered_at": 1784435887524,
  "hash_preview": "99a59f0e7574efea...",
  "ownership_verified": false
}