domhaul
Registry code: 8ffc97ca7ff1b541
Check if domain names are really available (live RDAP), with prices, brand scores and resale value.
from a public catalogue that lists it, not from the operator
- endpoint
- https://www.domhaul.com/api/mcp/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is domhaul live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is domhaul free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does domhaul have?
- 2 tools: check_domains, get_tld_prices.
- Is domhaul safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_domains unknown 1h ago
Check whether domain names are actually available to register, using live registry (RDAP) data. Use this when suggesting domain names (verify availability before presenting them, never assume a name is unregistered) or when the user asks whether specific domains are available. Accepts up to 50 fully-qualified domains (e.g. 'brewlog.app'). Returns availability, the registrar for taken domains, a 0-100 brandability score, an estimated resale value, the price in USD (price_usd for term_years, quote it rather than estimating; price_source 'checkout' is the expected charge at buy_url, confirmed before payment), and buy_url, the domhaul checkout page where the user can purchase the domain. If too few names are available, generate more candidates and call again.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domains" ], "properties": { "domains": { "type": "array", "items": { "type": "string" }, "maxItems": 50, "minItems": 1, "description": "Fully-qualified domain names to check, e.g. ['brewlog.app', 'getbrewlog.com']. Max 50." } } }arguments 18 linesget_tld_prices unknown 1h ago
Get registrar retail first-year price estimates in USD for top-level domains (.com, .io, .app, .dev, .ai, …). Use this when the user is comparing TLD options, e.g. 'should I get the .com or the .io?'. For the exact purchase price of a specific domain, use check_domains instead.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "tlds" ], "properties": { "tlds": { "type": "array", "items": { "type": "string" }, "maxItems": 20, "minItems": 1, "description": "TLDs to price, with or without the leading dot, e.g. ['com', '.io', 'app']" } } }arguments 18 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8ffc97ca7ff1b541.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8ffc97ca7ff1b541/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8ffc97ca7ff1b541?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.