@proof-holdings/mcp-server

Official

by ProofHoldings

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

list_authorizations

Read-only

Retrieve paginated authorizations and filter them by status, channel, or phone number to find specific access grants.

Instructions

List authorizations 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.

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.

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

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?

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful behavioral context by stating pagination and the Proof account / PROOF_API_KEY requirement, including a specific authentication caveat about start_login.

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 description is short and front-loaded with the core purpose before the access caveat. Every sentence carries useful information, though the access note is somewhat procedural.

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?

The tool is a straightforward filtered list with full schema coverage, an output schema, and read-only annotations. The description covers purpose, pagination, and authentication prerequisites; only sibling-selection guidance is missing.

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%, and the schema already documents page, limit, and each filter. The description mentions optional filters and pagination but adds no syntax or semantic detail beyond the schema, so baseline 3 is appropriate.

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 states a specific verb and resource: list authorizations, with optional filters and paginated results. It distinguishes the resource clearly enough, though it does not explicitly contrast with sibling tools like list_auth_sessions or export_authorizations.

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?

It gives a clear access prerequisite and explicitly notes that start_login does not unlock this tool. However, it provides no guidance on when to use this versus get_authorization, export_authorizations, or other listing tools.

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

Deploy Server