Proof Holdings

list_verification_requests

Read-only

List verification requests with optional filters. Returns paginated results.

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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`page`	No	Page number
`limit`	No	Items per page
`status`	No	Filter by status. 'active' = live (not-yet-expired) pending or partial requests; persisted statuses are time-aware.
`reference_id`	No	Filter by reference ID

Output Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	Yes	Pagination info in list responses

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "action_type": {
+            "type": "string"
+          },
+          "asset_count": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "completed_at": {
+            "type": "string"
+          },
+          "computed_state": {
+            "additionalProperties": {},
+            "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": {
+            "type": "string"
+          },
+          "progress": {
+            "additionalProperties": {},
+            "properties": {
+              "completed": {
+                "maximum": 9007199254740991,
+                "minimum": -9007199254740991,
+                "type": "integer"
+              },
+              "completed_required": {
+                "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",
+              "total"
+            ],
+            "type": "object"
+          },
+          "reference_id": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "status",
+          "computed_state",
+          "action_type",
+          "asset_count",
+          "progress",
+          "expires_at",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "description": "Pagination info in list responses",
+      "properties": {
+        "limit": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "page": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "total": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "total_pages": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "pagination"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```
First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real context on top: pagination behavior and an explicit auth precondition, including the non-obvious warning that start_login does not authorize this tool. That last point is the kind of trap an agent would otherwise hit. It stops short of describing result ordering or default page size.

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?

Purpose and return shape are front-loaded in one sentence, then the operational caveat follows as a labeled block. The ACCESS section is slightly verbose for the information it carries, but every clause (account requirement, authenticate step, start_login caveat) is actionable rather than filler.

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?

With a full output schema present, return-value detail is not needed, and schema coverage is complete, so the description's remaining job is auth and positioning. It handles auth thoroughly and notes pagination. The one gap is disambiguation from the cluster of sibling list/get tools, which an agent selecting among ~140 tools would want.

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 description coverage is 100%, so page, limit, status, and reference_id are all documented in the schema itself, including the time-aware meaning of 'active'. The description adds only the generic phrase 'optional filters' and 'paginated results', which does not extend parameter meaning beyond the schema. Baseline 3 applies.

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 first sentence gives a specific verb and resource ('List verification requests') plus the scoping detail that filters are optional and results are paginated. It never distinguishes this from the many adjacent listing tools (list_verifications, list_incoming_requests, list_my_requests, get_verification_request), so an agent must infer which collection it is looking at.

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 paragraph is a solid prerequisite note — it says an authenticated Proof account is required and that start_login will not unlock this tool, which is genuinely useful routing guidance. However, there is no when-to-use guidance relative to alternatives: nothing says to use this for enumerating requests versus get_verification_request for a single one, or how it differs from the other list_* tools.

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.