@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

list_webhook_deliveries

Read-only

Retrieve webhook delivery attempts with pagination and filtering to inspect status, response codes, and timestamps for debugging and monitoring.

Instructions

List webhook delivery attempts with pagination and filtering. Shows delivery status, response codes, and timestamps.

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 delivery status
`event_type`	No	Filter by event type (e.g. verification.completed)
`profile_id`	No	Only this sub-account's deliveries
`endpoint_id`	No	Only deliveries to this webhook endpoint
`verification_request_id`	No	Only deliveries for this verification request

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.7.2Nov 6, 2026

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

addedInput schema / properties / endpoint_id

Added value: +{
+  "description": "Only deliveries to this webhook endpoint",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

addedInput schema / properties / profile_id

Added value: +{
+  "description": "Only this sub-account's deliveries",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

addedInput schema / properties / verification_request_id

Added value: +{
+  "description": "Only deliveries for this verification request",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "attempts": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "delivered_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "endpoint_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "error_message": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "event_type": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "last_attempt_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "max_attempts": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "next_retry_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "profile_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "response_status": {
+            "anyOf": [
+              {
+                "maximum": 9007199254740991,
+                "minimum": -9007199254740991,
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "status": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "verification_request_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "verification_request_id",
+          "endpoint_id",
+          "profile_id",
+          "event_type",
+          "url",
+          "status",
+          "attempts",
+          "max_attempts",
+          "last_attempt_at",
+          "next_retry_at",
+          "delivered_at",
+          "response_status",
+          "error_message",
+          "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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the tool requires a Proof account with PROOF_API_KEY set and a server restart, and explicitly warns that start_login will not unlock it. It does not state default page size or ordering, so it stops short of a 5.

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 core capability front-loaded and the access requirement clearly separated. No filler sentences, though the blocking warning could be tightened into one line.

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 read-only, 7-param list tool with a full schema and an output schema, the description covers capability, filters, returned fields, and the authentication prerequisite. Only the absence of ordering/default-pagination behavior keeps it from complete.

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%, with every filter (status enum, event_type, profile_id, endpoint_id, verification_request_id) already documented in the schema. The description only restates that pagination and filtering exist, adding no semantics beyond the structured fields, so the 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 webhook delivery attempts") plus the fields returned, so it is distinguishable from get_webhook_delivery (singular) and list_webhook_endpoints. It does not explicitly name those siblings as alternatives, which keeps it 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?

Usage is implied by the name and the access note, but there is no guidance on when to use this versus get_webhook_delivery for a single attempt, get_webhook_stats for aggregates, or retry_webhook_delivery. The ACCESS paragraph is a prerequisite, not a when-to-use rule.

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

Deploy Server