Is the Hood Name Service MCP server down?

mcp-registry/ag.hood/name-service · v0.1.0

healthy
Last checked 2026-10-26 18:25 UTC · handshake 179ms

As of 2026-10-26 18:25 UTC, the Hood Name Service MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
99.8%
checks observed
4,712
outages (90d)
7
tools
5

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

Point your MCP client at this streamable-http endpoint: https://www.hood.ag/api/mcp

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 2 warning(s) across 5 tool(s); ~370 tokens of tool definitions.
Scores higher than 10% of 15,767 MCP servers Glimind has audited.
Its tool list costs an agent ~370 tokens per session — lighter than 95% of servers.
73 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions48
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_availability, name_info, resolve_name, resolve_text, reverse_resolve

3 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: check_availability, name_info, resolve_text

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fag.hood%2Fname-service/fixes

check_availability 1 change 
{
  "name": "check_availability",
  "description": "Check whether a .hood name is available to register, and its yearly price.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
name_info 1 change 
{
  "name": "name_info",
  "description": "Full snapshot of a .hood name: resolved address, NFT owner, expiry, and availability.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
resolve_name 1 change 
{
  "name": "resolve_name",
  "description": "Forward-resolve a .hood name to the address it points to. Returns null if unset.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "A .hood name, e.g. \"robin.hood\" (suffix optional)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ag.hood/name-service"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ag.hood/name-service"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fag.hood%2Fname-service.svg)](https://glimind.com/server/mcp-registry%2Fag.hood%2Fname-service?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fag.hood%2Fname-service?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fag.hood%2Fname-service.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fag.hood%2Fname-service.svg
   :target: https://glimind.com/server/mcp-registry%2Fag.hood%2Fname-service?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0c446e5263479a12…, first seen 2026-10-17, included at leaf 4386 of 74,700. Version history · verify what your client received.

Tools (5)

Compare: most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Hood Name Service MCP server down right now?

As of 2026-10-26 18:25 UTC, the Hood Name Service MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 10 minutes.

How many tools does Hood Name Service MCP server provide?

Hood Name Service MCP server advertises 5 tools, including check_availability, name_info, resolve_name, resolve_text, reverse_resolve.

How do I install Hood Name Service MCP server?

Point your MCP client at this streamable-http endpoint: https://www.hood.ag/api/mcp

Is the Hood Name Service MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Hood Name Service MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve