@proof-holdings/mcp-server

Official

by ProofHoldings

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

get_verification_request

Read-only

Fetch a verification request by ID to review all asset verification statuses and confirm each verification outcome.

Instructions

Get a verification request by ID. Returns the request with all its asset verification statuses.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

Name	Required	Description	Default
`id`	Yes	Verification request ID

Output Schema

Name	Required	Description
`id`	Yes	MongoDB ObjectId
`assets`	Yes
`status`	Yes	Status of a verification request
`progress`	No
`created_at`	Yes
`expires_at`	Yes
`partial_ok`	Yes
`updated_at`	No
`action_type`	Yes	Type of action for verification request or authorization
`callback_url`	No	The webhook URL set on the request, if any
`completed_at`	No
`redirect_url`	No
`reference_id`	No
`action_context`	No	The action the person is asked to authorize; null when the request carries none
`computed_state`	No	Additive machine-readable effective state: re-derives expiry from expires_at (never trusts the stored status). BOTH `is_expiring_soon` and `next_action` are role-aware — `next_action.role` says which side this envelope was computed for, and the two fields are consistent within it. Present only on authenticated owner/requester and recipient responses; absent on public/third-party surfaces.
`verification_url`	No	URL for the verification flow
`validity_requirement`	No	Required proof freshness as set on the request (e.g. "7d"); null when none was set

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.7.2Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Multi-asset verification request",
+  "properties": {
+    "action_context": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "amount": {
+              "type": "number"
+            },
+            "currency": {
+              "type": "string"
+            },
+            "description": {
+              "type": "string"
+            },
+            "entity": {
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The action the person is asked to authorize; null when the request carries none"
+    },
+    "action_type": {
+      "description": "Type of action for verification request or authorization",
+      "type": "string"
+    },
+    "assets": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "allowed_channels": {
+            "anyOf": [
+              {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "channel": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "has_proof": {
+            "type": "boolean"
+          },
+          "identifier": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "required": {
+            "type": "boolean"
+          },
+          "status": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "verified_at": {
+            "type": "string"
+          },
+          "verified_channel": {
+            "type": "string"
+          },
+          "verified_identifier": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "required",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "callback_url": {
+      "description": "The webhook URL set on the request, if any",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "completed_at": {
+      "type": "string"
+    },
+    "computed_state": {
+      "additionalProperties": {},
+      "description": "Additive machine-readable effective state: re-derives expiry from expires_at (never trusts the stored status). BOTH `is_expiring_soon` and `next_action` are role-aware — `next_action.role` says which side this envelope was computed for, and the two fields are consistent within it. Present only on authenticated owner/requester and recipient responses; absent on public/third-party surfaces.",
+      "properties": {
+        "is_expiring_soon": {
+          "type": "boolean"
+        },
+        "next_action": {
+          "additionalProperties": {},
+          "properties": {
+            "code": {
+              "type": "string"
+            },
+            "label": {
+              "type": "string"
+            },
+            "role": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "code",
+            "role",
+            "label"
+          ],
+          "type": "object"
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "is_expiring_soon",
+        "next_action"
+      ],
+      "type": "object"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "expires_at": {
+      "type": "string"
+    },
+    "id": {
+      "description": "MongoDB ObjectId",
+      "type": "string"
+    },
+    "partial_ok": {
+      "type": "boolean"
+    },
+    "progress": {
+      "additionalProperties": {},
+      "properties": {
+        "completed": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "completed_required": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "optional": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "required": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "total": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "completed",
+        "completed_required",
+        "required",
+        "optional",
+        "total"
+      ],
+      "type": "object"
+    },
+    "redirect_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reference_id": {
+      "type": "string"
+    },
+    "status": {
+      "description": "Status of a verification request",
+      "type": "string"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "validity_requirement": {
+      "description": "Required proof freshness as set on the request (e.g. \"7d\"); null when none was set",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verification_url": {
+      "description": "URL for the verification flow",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "status",
+    "assets",
+    "action_type",
+    "partial_ok",
+    "expires_at",
+    "created_at"
+  ],
+  "type": "object"
+}

First observedv1.1.0Sep 9, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already state readOnlyHint=true, and the description is consistent with that. Beyond annotations it discloses the access prerequisite (a Proof account, PROOF_API_KEY set, server restart) and that login-based flows do not unlock this tool — meaningful operational context. It does not describe behavior for invalid or inaccessible IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight blocks: what it does and returns first, then the access prerequisite. No filler, and the most important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be restated, and the description still summarises it in one clause. The authentication barrier — the main practical obstacle to a successful call — is covered. The only gap is lack of guidance for lookup by reference or listing, which sits with siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single required `id` parameter, and the description adds no format, prefix, or sourcing detail beyond "Verification request ID." Baseline 3 is appropriate when the schema fully documents the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Get a verification request by ID") and adds what is returned ("the request with all its asset verification statuses"). It does not explicitly distinguish itself from near-neighbours like get_verification or get_request_by_reference, so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is clear: call it with a request ID. It also explicitly rules out an alternative path by warning that "start_login does NOT open this tool," which is concrete when-not guidance. It does not cover siblings such as get_request_by_reference or list_verification_requests for lookup by other keys.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server