_ registry / mcp streamable-http · checked 47m ago

nomok

https://nomok.app

Registry code: cb8a9c912120d24f

api record

Use check_name to check one name on 70+ platforms (domains, social networks, marketplaces…), check_domains to compare several name ideas on domain extensions, suggest_names for available variants. Report "manual" and "unknown" results as unverified, never as available. Results are live checks, cached 10 minutes.

endpoint
https://nomok.app/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 nomok live?
Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
Is nomok free to use?
Yes — the hub reached it with no key and no payment.
What tools does nomok have?
3 tools: check_domains, check_name, suggest_names.
Is nomok 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
231ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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_domains unknown 47m ago

    Checks domain name availability for up to 10 names on chosen extensions (DNS + RDAP registry lookup). Default extensions: .com, .net, .org, .io, .app, .dev, .co, .fr. Supported: .com, .fr, .net, .org, .info, .biz, .co, .de, .uk, .it, .es, .be, .ch, .nl, .eu, .ca, .us, .io, .ai, .me, .gg, .tv, .app, .dev, .tech, .studio, .design, .art, .shop, .store, .online, .xyz. Ideal to compare several name ideas quickly. Available domains come with a registration link and indicative price.

    mcp-tool

    {
      "type": "object",
      "required": [
        "names"
      ],
      "properties": {
        "tlds": {
          "type": "array",
          "items": {
            "enum": [
              "com",
              "fr",
              "net",
              "org",
              "info",
              "biz",
              "co",
              "de",
              "uk",
              "it",
              "es",
              "be",
              "ch",
              "nl",
              "eu",
              "ca",
              "us",
              "io",
              "ai",
              "me",
              "gg",
              "tv",
              "app",
              "dev",
              "tech",
              "studio",
              "design",
              "art",
              "shop",
              "store",
              "online",
              "xyz"
            ],
            "type": "string"
          },
          "description": "Extensions to check, without dot (default: main ones)"
        },
        "names": {
          "type": "array",
          "items": {
            "type": "string",
            "description": "Domain label without extension, e.g. \"acme\""
          },
          "maxItems": 10,
          "minItems": 1
        }
      },
      "additionalProperties": false
    }
    arguments 59 lines
  • check_name unknown 47m ago

    Checks whether a name/handle is available on 70+ platforms at once: domain names (.com, .fr, .io, .app…), social networks (Instagram, TikTok, X, YouTube…), creative and dev platforms (GitHub, Behance…), e-commerce, freelance, gaming and company registries. Takes 5-15 s on first call (results cached 10 min). Statuses: available, likely_available, taken, manual (cannot be checked automatically), unknown (check failed). Never present manual/unknown results as available. Available domains come with a registration link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 50,
          "minLength": 2,
          "description": "Name or handle to check (2-50 chars: letters, digits, . - _)"
        },
        "categories": {
          "type": "array",
          "items": {
            "enum": [
              "social",
              "creative",
              "domain",
              "ecommerce",
              "local",
              "freelance",
              "gaming",
              "business",
              "other"
            ],
            "type": "string"
          },
          "description": "Optional: only return these categories (all by default)"
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • suggest_names unknown 47m ago

    Generates common variants of a name (get-, try-, -hq, -app, -studio…) and checks which ones are available as a domain (.com by default). Use when the exact name is taken.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "tld": {
          "enum": [
            "com",
            "fr",
            "net",
            "org",
            "info",
            "biz",
            "co",
            "de",
            "uk",
            "it",
            "es",
            "be",
            "ch",
            "nl",
            "eu",
            "ca",
            "us",
            "io",
            "ai",
            "me",
            "gg",
            "tv",
            "app",
            "dev",
            "tech",
            "studio",
            "design",
            "art",
            "shop",
            "store",
            "online",
            "xyz"
          ],
          "type": "string",
          "description": "Extension to check, default com"
        },
        "name": {
          "type": "string",
          "description": "Base name, letters/digits/hyphens"
        }
      },
      "additionalProperties": false
    }
    arguments 51 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 cb8a9c912120d24f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cb8a9c912120d24f/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/cb8a9c912120d24f/badge.svg)](https://brick.blue/agent/cb8a9c912120d24f?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.