namehound
Registry code: 3474f5a450023d3f
NameHound checks whether one specific brand, business or project name is free as a domain name (.com, .net, .org, .app) and as a handle on Bluesky, Mastodon, GitLab, npm and PyPI, using each service's own public lookup, and gives the NameHound Brand Name Score. One name per call. Results are a snapshot with the time they were checked; availability can change, the registrar or platform has the final say, and nothing here is legal or trademark advice. It does not suggest names, check lists of names, or check Instagram, X, TikTok, YouTube, GitHub or other platforms that block automated checks.
- endpoint
- https://namehound.app/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 namehound live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is namehound free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does namehound have?
- 1 tool: check_name_availability.
- Is namehound 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 1 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_name_availability unknown 1h ago
Use this when someone asks whether one specific brand, business, product or project name is free as a domain name (.com, .net, .org, .app) and as a handle on Bluesky, Mastodon, GitLab, npm and PyPI, and wants the NameHound Brand Name Score (0-100) for it. Send one name per call, for example "Blue Fern Studio". The name is made into a handle (lowercase letters and numbers). Returns up to 4 rows, each with the check time, the official source and a link to the NameHound page for that name. Results are a snapshot: availability can change, the registrar or platform has the final say, and this is not legal or trademark advice (the score leaves out the trademark part until the person runs the free USPTO search themselves). Do not use it to brainstorm names, to check a list of names, for trademark clearance, or for Instagram, X, TikTok, YouTube, GitHub or other platforms it does not check. It has a small daily limit, so call it only for names the person actually cares about.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 40, "minLength": 2, "description": "A specific name, e.g. \"Blue Fern Studio\". 2-40 characters. Wildcards and \"all\" are not accepted." } } }arguments 15 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 id3474f5a450023d3f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3474f5a450023d3f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3474f5a450023d3f?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.