@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

get_verified_user

Read-only

Retrieve a single verified user and their verifications by external user ID; requires a Proof account and configured PROOF_API_KEY.

Instructions

Get a single verified user and their verifications by external user ID.

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	Default
`external_user_id`	Yes	The external user ID

Output Schema

Name	Required	Description	Default
`verifications`	No
`types_verified`	No
`external_user_id`	No
`verification_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.7.2Nov 6, 2026

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "external_user_id": {},
+    "types_verified": {},
+    "verification_count": {},
+    "verifications": {}
+  },
+  "type": "object"
+}

First observedv1.1.0Sep 9, 2026

TDQS

A3.9/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 set by structured data; the description adds real value by disclosing the authentication/environment requirement and the restart-and-retry loop. It does not describe what happens when the user is unknown or unverified, which is the main behavioral gap.

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 sentences, front-loaded with the action and scope, then a clearly labeled ACCESS block. The restart instruction is slightly operational boilerplate but earns its place by preventing a failed call.

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 an output schema present, return shape need not be explained, and the auth prerequisite is covered. What is missing is failure behavior for nonexistent or unverified users, which matters for a lookup tool keyed on an external identifier.

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?

There is one parameter with 100% schema description coverage, so the schema already documents it. The description only restates that the lookup key is an external user ID, adding no format or sourcing detail beyond that.

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 — retrieving one verified user plus their verifications, keyed by external user ID. The word 'single' implicitly separates it from list_verified_users, though no sibling is named explicitly, which keeps it just 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete precondition (a Proof account with PROOF_API_KEY set) and an explicit exclusion — start_login will not unlock this tool — which steers the agent away from a plausible wrong path. It stops short of saying when to prefer this over list_verified_users or get_user_domain_verification_status.

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

Deploy Server