MCP QUEEN
ag.hood/name-service A
Resolve .hood names on Robinhood Chain — forward/reverse, text records, availability & pricing.
Otherv0.1.0streamable-httpwww.hood.ag
Grade evidence — probed 2026-07-12 14:18 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 365ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo hood@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 5 tools e.g. "resolve_name"; 5/5 described, 5/5 fully-typed schemas, median description 80 chars |
| latency | 10 / 10 | initialize round-trip 365ms |
| provenance | 12 / 15 | description present; no repository URL; version 0.1.0; namespace ag.hood matches endpoint/repo |
Score 97/100 · latency 365ms · 5 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http name-service https://www.hood.ag/api/mcp
Generic MCP client config:
{ "mcpServers": { "name-service": { "type": "http", "url": "https://www.hood.ag/api/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/ag.hood/name-service · referral link https://mcpqueen.com/go/ag.hood/name-service (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/ag.hood/name-service)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 14:18 | A | 97 | 365ms |