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

namesake-discovery

https://namesake.baby

Registry code: 7fcea7c2f3a06e48

api record

Read-only access to Namesake's baby name catalog: meaning, origin, pronunciation, popularity trend.

from a public catalogue that lists it, not from the operator

endpoint
https://www.namesake.baby/api/mcp
door code
dae9ca61cff66b22
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 namesake-discovery live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is namesake-discovery free to use?
Yes — the hub reached it with no key and no payment.
What tools does namesake-discovery have?
7 tools: get_name, get_guide, get_similar_names, get_cultural_classification, search_names, list_guides, list_namesake_feeds.
Is namesake-discovery 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
99.5%

90 days 99.5%· all time 99.4%

latency
628ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1321 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • look up a baby name's meaning and origin
  • search baby names
  • find similar sounding names
  • read baby naming guides
takes → gives
text → data
tools
7 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

_ what it can do 7 tools
2 open 5 never probed 2 of 7 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.

  • list_guides reads open 12h ago

    List every published, free-to-read baby-naming guide on this host. Known topics (8): how-to-choose-a-baby-name, baby-name-checklist, partner-disagreement, baby-name-popularity, pronunciation-test, gender-neutral-names, most-culturally-driven-names-last-decade, why-names-go-in-and-out-of-fashion.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_namesake_feeds reads open 4h ago

    List Namesake's free machine-readable feeds and their MCP/REST availability. OpenAPI is also published at https://www.namesake.baby/openapi.json.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_name reads unknown 20h ago

    Returns one baby name's public profile: meaning, origin, pronunciation, syllables, style/vibe tags, popularity rank + trend, and the Namesake score breakdown.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The name, case-insensitive (e.g. Rowan)."
        }
      }
    }
    arguments 13 lines
  • get_guide reads unknown 20h ago

    Returns one guide's full content (title, intro, sections) — the same content the human page renders; every guide on this host is free to read. Known topics (8): how-to-choose-a-baby-name, baby-name-checklist, partner-disagreement, baby-name-popularity, pronunciation-test, gender-neutral-names, most-culturally-driven-names-last-decade, why-names-go-in-and-out-of-fashion.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "type": "string",
          "description": "Guide topic slug (e.g. how-to-choose-a-baby-name)."
        }
      }
    }
    arguments 13 lines
  • get_similar_names reads unknown 20h ago

    Returns phonetic neighbors for a baby name from the research neighborhood graph — the same sounds-like list the /names/[slug] profile panel shows. Does not invent neighbors.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The name, case-insensitive (e.g. Rowan)."
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Max neighbors to return (default 8, max 20)."
        }
      }
    }
    arguments 19 lines
  • get_cultural_classification reads unknown 4h ago

    Returns the Phase 5 null-model cultural classification for a baby name (strongly cultural / culturally influenced / partial / fashion drift) — the same badge the name profile shows.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The name, case-insensitive (e.g. Rowan)."
        }
      }
    }
    arguments 13 lines
  • search_names reads unknown 4h ago

    Search the baby name catalog by prefix/substring. Returns name, origin, short meaning, 2024 SSA popularity rank, Namesake score, and trend label, ordered by popularity.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max rows to return (default 10, max 50)."
        },
        "query": {
          "type": "string",
          "description": "Name prefix/substring, at least 2 characters (e.g. \"Row\")."
        }
      }
    }
    arguments 19 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 7fcea7c2f3a06e48.

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

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.