Taproot: AT Protocol MCP

verify_handle

Read-only

Bidirectionally verify that a handle is really owned by its DID, via DNS TXT and HTTPS well-known. Returns whether each method passed. Use this to check for impersonation/spoofing,search results and resolve give candidates, this gives cryptographic binding.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handle": "<handle>"
    },
    "name": "verify_handle"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes	A handle, e.g. alice.bsky.social.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that verification happens through two independent external mechanisms (DNS TXT and HTTPS well-known) and that per-method pass/fail is reported. This tells the agent it makes outbound network lookups and returns granular results, which the annotations alone do not 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?

The core operation is front-loaded in the first sentence, which is efficient. The trailing clause 'this gives cryptographic binding' is mildly redundant with 'Bidirectionally verify' and the run-on comma splicing slightly muddies the ending.

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, the description need not detail return values, and it still usefully notes that per-method results are returned. For a single-parameter, low-complexity verification tool it covers purpose, mechanism, and routing to alternatives adequately.

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 a single required 'handle' parameter with 100% schema description coverage, including an example (alice.bsky.social). The description adds no format or syntax guidance beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a specific verb (verify) and resource (handle ownership by DID) and specifies the two mechanisms used: DNS TXT and HTTPS well-known. This is clearly distinct from siblings like resolve or search_accounts, which the description itself characterizes as producing mere candidates.

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 states a purpose-driven use case (checking for impersonation/spoofing) and contrasts itself with resolve/search results, which only 'give candidates' while this 'gives cryptographic binding.' The phrasing is slightly garbled and no explicit when-not-to-use case is given, so it falls short of 5.

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

All Taproot: AT Protocol MCP 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.

Resources

Need Help?