nostr-ops-mcp

nostr_verify_nip05

Validate a NIP-05 identifier by resolving its well-known nostr.json, confirm expected pubkey match, and return relay hints.

Instructions

Verify a NIP-05 identifier resolves to the expected pubkey. Fetches https://{domain}/.well-known/nostr.json?name={name} and looks up names[name]. If expected_pubkey is provided, returns verified=true only if the resolved pubkey matches; otherwise returns verified=true on any successful resolution + the resolved pubkey. Also surfaces the recipient's relay hints if the well-known doc advertises them (NIP-65 outbox path).

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": {
      "identifier": "<identifier>"
    },
    "name": "nostr_verify_nip05"
  }
}

Input Schema

Name	Required	Description	Default
`identifier`	Yes	NIP-05 identifier. Either `name@domain.tld` (e.g., `alice@getalby.com`) or a bare `domain.tld` (resolves the `_@domain.tld` root identity).
`expected_pubkey`	No	Optional. If provided, the tool returns verified=true only when the resolved pubkey matches.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Jul 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description bears full burden. It explains the HTTP fetch, JSON lookup, verification logic, and relay hints. It does not mention failure modes or performance, but provides substantial transparency.

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?

Description is a single paragraph that covers key points without excess. It could be slightly more structured, but it remains concise and informative.

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?

No output schema, so description must hint at returns. It mentions verified flag, resolved pubkey, and relay hints, which is reasonably complete for a verification tool. Lacks explicit return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with param descriptions. Description adds meaning beyond schema by explaining the fetch URL and lookup process, providing context for how parameters are used.

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?

The description clearly states it verifies a NIP-05 identifier and resolves to a pubkey, using specific verb 'Verify' and resource 'NIP-05 identifier'. It distinguishes from sibling tools like nostr_get_profile by focusing on verification.

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?

The description explains when to use the tool (to verify a NIP-05 identifier) and details behavior with and without expected_pubkey. It does not explicitly state when not to use or compare to siblings, but context is clear.

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

Deploy Server