@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

check_domain_verification

Checks a pending domain verification by triggering a DNS/HTTP lookup and returning the updated status. Use it to confirm whether domain ownership is verified.

Instructions

Check the status of a pending domain verification. Triggers a DNS/HTTP check and returns the updated status.

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
`id`	Yes	Domain verification ID

Output Schema

Name	Required	Description
`id`	No	MongoDB ObjectId
`domain`	No
`status`	No
`verified`	No
`check_count`	No
`verified_at`	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": {
+    "check_count": {},
+    "domain": {},
+    "id": {
+      "description": "MongoDB ObjectId"
+    },
+    "status": {},
+    "verified": {},
+    "verified_at": {}
+  },
+  "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 annotations mark this as non-read-only and non-destructive, and the description explains why: it triggers a network DNS/HTTP check as a side effect and returns an updated status rather than cached data. The access paragraph adds credential requirements and a restart step, which the annotations cannot convey.

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 tight sentences deliver purpose and side effect, then a clearly separated access block. Every sentence carries information; only slight redundancy between 'check the status' and 'returns the updated status'.

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?

An output schema is present, so return values need no explanation, and the critical operational prerequisite (Proof account, PROOF_API_KEY, server restart) is stated. For a one-parameter tool this is essentially complete; only comparison to sibling verification tools 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 coverage is 100% and the single 'id' parameter is already described as the 'Domain verification ID'. The description reinforces that the ID refers to a pending verification rather than a domain, but adds no syntax or format detail beyond the schema.

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 ('Check the status') and resource ('pending domain verification') and adds that it triggers a live DNS/HTTP check, which separates it from passive readers like get_verification or get_domain. It does not name a specific sibling as the alternative, so it falls short of full sibling differentiation.

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 phrase 'pending domain verification' implies usage scope (only after a verification was started), and the ACCESS paragraph usefully explains the account prerequisite and that start_login will not unlock this tool. However, it never says when to prefer this over verify_domain, trigger_verification, or start_domain_verification, which are close siblings.

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

Deploy Server