@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

list_verification_requests

Read-only

Lists verification requests with optional status and reference filters, returning paginated results for review or tracking.

Instructions

List verification requests with optional filters. Returns paginated results.

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
`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.

Changed3 schema fields changedv1.7.2Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

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

First observedv1.1.0Sep 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations supply readOnlyHint=true, and the description adds real operational context beyond that: paginated responses and the hard prerequisite of a Proof account with PROOF_API_KEY set and a server restart. It does not disclose default/max page size or what happens when filters match nothing, but the access profile is well covered.

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?

Three short sentences, front-loaded with purpose then result shape then the access gate, with no filler. The ACCESS block is slightly imperative-heavy but every sentence carries actionable information.

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

Completeness3/5

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

Output schema exists and pagination and auth are covered, so return values and setup are adequately handled. The gap is disambiguation: with an extremely dense sibling set of request/verification list tools, leaving the reader to infer scope (own requests? incoming? all?) is a material omission.

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%, including the non-obvious 'active' vs persisted status semantics, so the schema does the heavy lifting. The description only says 'optional filters' and adds no meaning beyond what the four documented parameters already carry; 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?

States a specific verb and resource ('List verification requests') plus result shape ('paginated results'). It does not distinguish itself from near-identical siblings in a crowded namespace (list_verifications, list_my_requests, list_incoming_requests, get_request_by_reference), so an agent cannot be certain which list to reach for.

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?

Gives a genuine when-not: it explicitly says start_login does NOT open this tool, saving a doomed login round-trip. However, it names no alternative tool and gives no criteria for choosing between this and the many other verification-listing siblings, so routing guidance is partial.

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

Deploy Server