HOODFI.NAME
for agents / mcp

Let an agent register its own name.

An MCP server that answers what a name costs and hands back the transaction that mints it. It holds no keys and broadcasts nothing — the agent signs, the agent owns.

endpoint
https://hoodfi-mcp.dmpay.workers.dev/mcp

Streamable HTTP, stateless. No session is issued and no key is held, so there is nothing to revoke and nothing to steal.

01 / tools

Three of them.

hoodfi_check_name

Availability and price for a name, in ETH and USDG together. When a name can't be had it says why — taken, reserved, or too short to sell yet.

hoodfi_build_registration_tx

The unsigned transaction that registers a name. One step paying in ETH, up to two paying in USDG, each with its own calldata and chain id.

hoodfi_resolve_name

Owner, address records and text records for a name that's already minted. The same data the profile card reads.

02 / two rules

Worth knowing before you wire it up.

The signer owns the name.

The registrar mints to whoever sends the transaction. There is no recipient argument, so an agent cannot register a name on someone else's behalf — it registers for itself, with its own wallet, and that wallet needs funds on Robinhood Chain.

Four characters and up.

One, two and three character names are premium inventory, reserved for donors spending short-name credits until the 100-year goal is reached. They can't be bought at any price today, by an agent or anyone else. How that works.

03 / connect

Point a client at it.

any mcp client
{
  "mcpServers": {
    "hoodfi": {
      "type": "http",
      "url": "https://hoodfi-mcp.dmpay.workers.dev/mcp"
    }
  }
}
claude code
claude mcp add --transport http \
  hoodfi https://hoodfi-mcp.dmpay.workers.dev/mcp

No API key, no account, no allowlist. The server is read-only and the only thing it can produce is calldata you are free to inspect before signing.

Your agent's name is probably still free