Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

check_domain_credentials

Read-only

Check whether stored DNS credentials have access to a domain before triggering verification, confirming the credentials work.

Instructions

Check if stored DNS credentials have access to a domain. Use before triggering verification to confirm the credentials work.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, or sign in with start_login — a session opens this tool — then call this tool again.

Input Schema

NameRequiredDescriptionDefault
idYesDomain ID to check credentials for

Output Schema

NameRequiredDescriptionDefault
suggestionNoSent when no credential can reach the domain.
has_credentialsYesWhether the account holds any valid DNS credential. When false, only `accessible_credentials` (empty), `detected_provider` and `suggestion` are sent.
detected_providerYes
registrar_providerNo
accessible_credentialsYes
has_accessible_credentialNo
has_registrar_credentialsNo
can_try_ownership_verificationNoA registrar credential can confirm ownership while the zone is served elsewhere.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Which of the account's DNS credentials can reach a domain",
+  "properties": {
+    "accessible_credentials": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "error": {
+            "type": "string"
+          },
+          "has_access": {
+            "type": "boolean"
+          },
+          "is_registrar": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider",
+          "name",
+          "has_access"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "can_try_ownership_verification": {
+      "description": "A registrar credential can confirm ownership while the zone is served elsewhere.",
+      "type": "boolean"
+    },
+    "detected_provider": {
+      "type": "string"
+    },
+    "has_accessible_credential": {
+      "type": "boolean"
+    },
+    "has_credentials": {
+      "description": "Whether the account holds any valid DNS credential. When false, only `accessible_credentials` (empty), `detected_provider` and `suggestion` are sent.",
+      "type": "boolean"
+    },
+    "has_registrar_credentials": {
+      "type": "boolean"
+    },
+    "registrar_provider": {
+      "type": "string"
+    },
+    "suggestion": {
+      "description": "Sent when no credential can reach the domain.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "has_credentials",
+    "accessible_credentials",
+    "detected_provider"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, and the description adds information the annotations do not carry: the tool operates on stored credentials and requires a Proof account, configured either via PROOF_API_KEY plus a server restart or via start_login. It does not explain what a negative result looks like (no credentials vs. insufficient permissions), but that is largely the output schema's job.

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 purpose and sequencing guidance are front-loaded in the first two sentences, and the ACCESS block is clearly separated. The access paragraph is slightly long relative to the tool's simplicity but is genuinely necessary setup 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?

With one parameter, an output schema, and a readOnly annotation, the definition covers the essentials, and the auth/bootstrap instructions are a real addition for a tool that will otherwise fail silently for unauthenticated agents. Only the mapping from a failed check to a next action is left implicit.

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 parameter 'id' is documented there as the domain ID. The description's phrase "a domain" adds no syntax or format detail beyond the schema, 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?

The first sentence gives a specific verb and resource: it checks whether stored DNS credentials have access to a given domain, which distinguishes it from verify_domain_with_credentials and trigger_verification. It stops short of naming the sibling it is not, so an agent must infer the boundary.

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?

"Use before triggering verification to confirm the credentials work" gives an explicit sequencing condition that ties it to trigger_verification. There is no explicit when-not guidance or named alternative for the case where credentials are absent (e.g., create_dns_credential).

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

Deploy Server

Other Tools