Proof Holdings

list_authorizations

Read-only

List authorizations 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_authorizations"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number
`limit`	No	Items per page
`phone`	No	Filter by phone number
`status`	No	Filter by authorization status
`channel`	No	Filter by channel

Output Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	Yes

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": {
+          "authorized_at": {
+            "type": "string"
+          },
+          "bsuid": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "business_name": {
+            "type": "string"
+          },
+          "channel": {
+            "type": "string"
+          },
+          "circle_id": {
+            "allOf": [
+              {
+                "type": "string"
+              },
+              {}
+            ]
+          },
+          "confirmations_sent": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "denied_at": {
+            "type": "string"
+          },
+          "enrolled": {
+            "type": "boolean"
+          },
+          "expires_at": {
+            "type": "string"
+          },
+          "hitl_id": {
+            "allOf": [
+              {
+                "type": "string"
+              },
+              {}
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_used_at": {
+            "type": "string"
+          },
+          "phone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "proof_token": {
+            "type": "string"
+          },
+          "recipient": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "recipient_display_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "revocation_reason": {
+            "type": "string"
+          },
+          "revoked_at": {
+            "type": "string"
+          },
+          "scope": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          },
+          "verification_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "status",
+          "channel",
+          "scope",
+          "business_name",
+          "recipient_display_name",
+          "enrolled",
+          "expires_at",
+          "confirmations_sent",
+          "created_at",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "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"
+        }
+      },
+      "required": [
+        "page",
+        "limit",
+        "total",
+        "total_pages"
+      ],
+      "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 genuinely non-obvious behavior: results are paginated, and authentication must go through the client's /mcp flow rather than start_login. The auth precondition is exactly the kind of context annotations cannot express. Return shape is covered by the output schema, so omitting it is fine.

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?

The functional sentence comes first and the access requirement is set off in its own block, which is appropriate for a precondition an agent must satisfy before every call. The capitalized 'ACCESS' header and the parenthetical Claude Code hint are slightly voicey but each carries information.

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 zero-required-parameter read tool with an output schema and a readOnlyHint, the description covers purpose, pagination, and the authentication gate. The only real gap is the missing routing hint toward get_authorization for single-record lookups and export_authorizations for bulk export.

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 all five parameters documented and enums declared for status and channel. The description's phrase 'optional filters' adds nothing beyond that, 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 authorizations') plus scope modifiers ('optional filters', 'paginated results'), so the operation is unambiguous. It does not distinguish itself from the closely-named siblings get_authorization (single item) or export_authorizations, leaving that differentiation to inference.

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 block gives concrete operational guidance: a Proof account is required, the client must be authenticated via /mcp, and start_login does NOT unlock this tool — that last point prevents a real failure loop. However, there is no guidance on when to use this list over get_authorization or export_authorizations.

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.