mcpbeat

hood. — .hood name service MCP Server

ag.hood/name-service
not responding

hood. — .hood name service is listed as active in the registry but did not answer our last check. It exposes 5 tools.

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

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 92 checks
5
Tools
read from the server
75 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add name-service --transport http https://www.hood.ag/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "name-service": {
      "url": "https://www.hood.ag/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.name-service]
url = "https://www.hood.ag/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "name-service": {
      "url": "https://www.hood.ag/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "name-service": {
      "url": "https://www.hood.ag/api/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

resolve
resolve_name
Forward-resolve a .hood name to the address it points to. Returns null if unset.
resolve_text
Read a text record (e.g. "avatar", "url", "com.twitter") set on a .hood name.
availability
check_availability
Check whether a .hood name is available to register, and its yearly price.
name
name_info
Full snapshot of a .hood name: resolved address, NFT owner, expiry, and availability.
reverse
reverse_resolve
Reverse-resolve an address to its primary .hood name. `verified` is true only when the name's forward record points back to the address.

Endpoints

URLTransportStateLatencyChecked
https://www.hood.ag/api/mcp streamable-http answering 75 ms 3 min ago

hood. — .hood name service — questions

Answers built from our own checks of this server.

What can hood. — .hood name service do?
It exposes 5 tools, read directly from the server on our last check. Among them: check_availability, name_info, resolve_name, resolve_text, reverse_resolve. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is hood. — .hood name service working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 75 ms. The bar chart above shows every period we have measured.
The registry lists hood. — .hood name service as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect hood. — .hood name service?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does hood. — .hood name service need an API key?
No. hood. — .hood name service completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.