_ registry / mcp streamable-http · checked 8h ago

findadomain-name

https://findadomain.name

Registry code: 330c28c3552b1dc5

api record

Findadomain.name generates domain ideas and checks their availability. It returns brandable names and any domain hacks supplied by the source. Availability checks can be unconfirmed. Registrar prices (no markup) appear when supplied by the current lookup, and keyword search-volume where the data exists. Use find_domains to brainstorm from an idea, search_domain to check one name across many extensions, and check_availability for a specific list of domains. Every result is sourced from the domain service: it reports failures instead of fabricating availability or prices. Links preserve the…

endpoint
https://findadomain.name/api/mcp
protocol
streamable-http ·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 it live, free and safe measured by this hub
Is findadomain-name live?
Partly — its last checks failed now and then (checked 8h ago). It answered 99% of checks over the last 30 days.
Is findadomain-name free to use?
Yes — the hub reached it with no key and no payment.
What tools does findadomain-name have?
3 tools: check_availability, find_domains, search_domain.
Is findadomain-name 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.
reachable
degraded
uptime, 30 days
98.5%

90 days 99.1%· all time 99.1%

latency
459ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 328 checks · signed record
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • brainstorm domain names for an idea
  • check availability of domains
  • compare prices across domain extensions
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

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

_ what it can do 3 tools
3 never probed 0 of 3 classified

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_availability reads unknown 2d ago

    Check availability for a specific list of full domains (e.g. ['acme.com','acme.ai']). Returns availability, renewal details where supplied, and a registrar link. This fast lookup does not supply a registration quote; use search_domain for prices. Up to 25 domains per call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domains"
      ],
      "properties": {
        "domains": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Full domain names to check, each including its extension (e.g. ['getacme.com','acme.ai']). Up to 25 at a time."
        }
      }
    }
    arguments 15 lines
  • find_domains reads unknown 2d ago

    Brainstorm domain names for an idea, product, or company. Returns brandable names and any domain hacks supplied by the source, with availability and monthly keyword search-volume where available. Cached ideas receive a new availability check, and a name it confirms as an ordinary registration (not premium) is priced at its extension's current standard rate. Unknown availability and missing registration quotes are null, never reused from an old search. Use search_domain for a fresh per-name quote or follow the registrar link. A new idea can take about a minute to generate: if the result has status 'generating', call find_domains again with the same arguments after retry_after_seconds, and that call returns the names.

    mcp-tool

    {
      "type": "object",
      "required": [
        "idea"
      ],
      "properties": {
        "idea": {
          "type": "string",
          "description": "The company name, product, or idea to generate domain names for. Example: 'an AI tool that writes SQL'."
        },
        "tlds": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Restrict results to these TLD extensions without the dot (e.g. ['com','ai','io']). Omit to let the finder pick the best-fitting extensions, including domain hacks."
        },
        "purpose": {
          "type": "string",
          "description": "Optional. What the domain is for (e.g. 'startup', 'blog', 'portfolio', 'saas'), to steer the style."
        },
        "description": {
          "type": "string",
          "description": "Optional. A longer description of the business, for more relevant names and better-fitting extensions."
        }
      }
    }
    arguments 27 lines
  • search_domain reads unknown 2d ago

    Request availability and current quotes for a specific name across supported TLD extensions at once. Give a bare label ('acme') to see acme.com, acme.io, acme.ai... or a full domain ('acme.io') to check that one. Availability, registration prices, and renewal details are returned when supplied, alongside a registrar link. Missing fields stay unconfirmed; confirm final terms at the registrar.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The name to check. A bare label ('acme') is expanded across many TLDs; a full domain ('acme.io') checks that exact domain."
        },
        "tlds": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Limit to these TLD extensions without the dot (e.g. ['com','co','io'])."
        },
        "exact_extension": {
          "type": "boolean",
          "description": "Optional. If the name already includes an extension, set true to check only that exact domain instead of expanding across TLDs."
        }
      }
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 330c28c3552b1dc5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/330c28c3552b1dc5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/330c28c3552b1dc5/badge.svg)](https://brick.blue/agent/330c28c3552b1dc5?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.

_ how we know
card completeness
70%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.