Skip to content

hood. — .hood name service

by hood.ag · remote · no sign-in to list tools · v0.1.0 · published by ag.hood

Resolve .hood names on Robinhood Chain — forward/reverse, text records, availability & pricing.

Changes · 2
CompareRegistry entry

5 tools: 2 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http name-service https://www.hood.ag/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 2Claude Code: ask
  • check_availabilityCheck whether a .hood name is available to register, and its yearly price.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check whether a .hood name is available to register, and its yearly price.
  • name_infoFull snapshot of a .hood name: resolved address, NFT owner, expiry, and availability.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full snapshot of a .hood name: resolved address, NFT owner, expiry, and availability.
Only reads 3Claude Code: allow
  • resolve_nameForward-resolve a .hood name to the address it points to.No findings

    Why it is in this group

    • The name "resolve_name" says "resolve": a word for reading.
    Description, as the server wrote it
    Forward-resolve a .hood name to the address it points to. Returns null if unset.
  • resolve_textRead a text record (e.g.No findings

    Why it is in this group

    • The name "resolve_text" says "resolve": a word for reading.
    Description, as the server wrote it
    Read a text record (e.g. "avatar", "url", "com.twitter") set on a .hood name.
  • reverse_resolveReverse-resolve an address to its primary .hood name.No findings

    Why it is in this group

    • The name "reverse_resolve" says "resolve": a word for reading.
    Description, as the server wrote it
    Reverse-resolve an address to its primary .hood name. `verified` is true only when the name's forward record points back to the address.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http name-service https://www.hood.ag/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__name-service__resolve_name",
      "mcp__name-service__reverse_resolve",
      "mcp__name-service__resolve_text"
    ],
    "ask": [
      "mcp__name-service__check_availability",
      "mcp__name-service__name_info"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as name-service. Review it before you use it.