hood. — .hood name service MCP Server

by hood Your server? Claim it

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 91 days of history · worst day 0%

91 days agonow

17.6%

Uptime 24h

16 of 91 checks

Tools

read from the server

258 ms

Response time

average over 24h

open, no key

Access

streamable-http

hood. — .hood name service does not always answer

Over the last week it answered 42.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "name-service": {
      "type": "http",
      "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

URL	Transport	State	Latency	Checked
https://www.hood.ag/api/mcp	streamable-http	answering	80 ms	8 min ago

Alternatives to hood. — .hood name service

same job, measured the same way

OrbitFour

by orbitfour

Check domain availability and live registry pricing, or search for available names.

4 tools answering

Namecheap

by codechap

MCP server for Namecheap — check availability, list domains, and get pricing

local only

three.ws Naming

by nirholas

On-chain identity for AI agents: resolve .sol names, reverse-lookup wallets, check handles.

138 installs/wk local only

DNSimple MCP by usefulapi

by usefulapi

MCP server for DNSimple — domains, DNS zone records, availability, pricing and contacts.

12 tools answering

izHost

by izhost

izHost public read-only MCP: service pricing and live domain availability lookup.

8 tools answering

Name.ai MCP Server

by name

Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.

4 tools answering

Namecheap

by ziggythebot

Check domain availability across 600+ TLDs on Namecheap with pricing and purchase links

37 installs/wk local only

Plumbing Booking

by thejohnsonbros

Johnson Bros. Plumbing: check coverage, services, pricing, availability, and book by SMS.

16 tools answering

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 16 of 91 checks got a reply (17.6%), average response time 258 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 in the form 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.

How fast is hood. — .hood name service?

It answers our handshake in 258 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.