Proof Holdings

get_verification_request

Read-only

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

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_verification_request"
  }
}

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
`outcome`	No	`relying_party` when the request was created to wait for your outcome; null otherwise. Absent from an API that predates the field.
`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
`outcome_timeout_seconds`	No	The window set on the request, in seconds; null when it does not wait for an outcome. Absent from an API that predates the field.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026

addedOutput schema / properties / assets / items / properties / outcome

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "deadline_at": {
+          "type": "string"
+        },
+        "decided_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reason": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "reason",
+        "deadline_at",
+        "decided_at"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / outcome

Added value: +{
+  "description": "`relying_party` when the request was created to wait for your outcome; null otherwise. Absent from an API that predates the field.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / outcome_timeout_seconds

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The window set on the request, in seconds; null when it does not wait for an outcome. Absent from an API that predates the field."
+}

Changed1 schema field changedNov 2, 2026

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"
+}

Changed1 schema field changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The readOnlyHint=true annotation is consistent with 'Get', and the description adds context the annotations do not carry: a Proof account is required and authentication is a prerequisite that start_login cannot satisfy. The remaining behavior, the return shape, is covered by the output schema, so this is close to complete.

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

Conciseness4/5

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

Two short paragraphs with the purpose front-loaded and the access caveat clearly separated. Every sentence carries information; the parenthetical Claude Code hint is slightly tool-specific but earns its place as actionable setup guidance.

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?

For a single-parameter read tool with an output schema and readOnlyHint already declared, the description covers the main failure mode an agent would hit (auth) and the return scope. Only the choice among sibling read tools is left unaddressed.

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?

There is a single parameter with 100% schema description coverage ('Verification request ID'), so the schema already does the work. The description only restates 'by ID' without adding format or sourcing guidance, which is the baseline for high coverage.

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 uses a specific verb and resource ('Get a verification request by ID') and states the scope of what is returned ('all its asset verification statuses'). It does not explicitly differentiate itself from nearby siblings such as list_verification_requests or get_request_by_reference, so it falls short of a 5.

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

Usage Guidelines3/5

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

The access note gives a real precondition (authenticate via /mcp, and start_login will not unlock this tool), which is useful routing information. However, it never states when to pick this tool over retrieval alternatives like get_verification, get_request_proofs, or get_request_by_reference, leaving selection to inference.

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

All Proof Holdings tools Inspect

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.