baby-registry
https://babyregistry.vercel.app
Registry code: dc55c2aa222ea160
Baby Registry MCP — build baby shopping lists and registries. Always pass marketplace + locale. Prefer search_catalog or search_suggest, then create_and_fill_registry (or create_registry + add_registry_item). Responses use buyUrl + trackingTag on amazon.se; affiliateUrl is a compat alias.
- endpoint
- https://babyregistry.vercel.app/api/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is baby-registry live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is baby-registry free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does baby-registry have?
- 6 tools: create_registry, resolve_product, search_suggest, create_and_fill_registry, add_registry_item, search_catalog.
- Is baby-registry 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 6 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.
create_registry unknown never probed
Create an empty baby registry / wishlist. Returns id, editToken, ownerUrl, shopUrl. Start of list-building. Requires marketplace + locale.
{ "type": "object", "required": [ "marketplace", "locale" ], "properties": { "locale": { "type": "string", "description": "End-user locale, e.g. en, en-US, sv-SE, de-DE" }, "ageBand": { "type": "string" }, "childName": { "type": "string" }, "interests": { "type": "array", "items": { "type": "string" } }, "marketplace": { "type": "string", "description": "Amazon storefront domain or id, e.g. amazon.se, amazon.com, us, se" } } }arguments 29 linesresolve_product unknown never probed
Resolve ASIN, Amazon URL, or keywords to a curated buy URL on the selected marketplace (buyUrl + trackingTag; affiliateUrl is a compat alias).
{ "type": "object", "required": [ "marketplace", "locale" ], "properties": { "url": { "type": "string" }, "asin": { "type": "string" }, "locale": { "type": "string", "description": "End-user locale, e.g. en, en-US, sv-SE, de-DE" }, "ageBand": { "type": "string" }, "category": { "type": "string" }, "keywords": { "type": "string" }, "marketplace": { "type": "string", "description": "Amazon storefront domain or id, e.g. amazon.se, amazon.com, us, se" } } }arguments 32 linessearch_suggest unknown 2h ago
Search Amazon for baby registry / shopping-list ideas. Rewrites queries with age/category cues. Use when building a recommendation list. Requires marketplace + locale.
{ "type": "object", "required": [ "q", "marketplace", "locale" ], "properties": { "q": { "type": "string", "description": "Search query (e.g. bassinet, bottle warmer)" }, "limit": { "type": "integer", "default": 10 }, "locale": { "type": "string", "description": "End-user locale, e.g. en, en-US, sv-SE, de-DE" }, "ageBand": { "type": "string", "description": "expecting | 0-3m | 3-6m | 6-12m | 12-24m | toddler" }, "interest": { "type": "string", "description": "sleep | feeding | diapering | gear | clothing | safety | play | bath" }, "marketplace": { "type": "string", "description": "Amazon storefront domain or id, e.g. amazon.se, amazon.com, us, se" } } }arguments 34 linescreate_and_fill_registry unknown never probed
One-shot registry/shopping-list builder: create a registry and fill from ASINs/keywords/queries. Best tool for agents building a full baby list. Returns ownerUrl + shopUrl + editToken. Requires marketplace + locale.
{ "type": "object", "required": [ "marketplace", "locale" ], "properties": { "locale": { "type": "string", "description": "End-user locale, e.g. en, en-US, sv-SE, de-DE" }, "ageBand": { "type": "string" }, "childName": { "type": "string" }, "interests": { "type": "array", "items": { "type": "string" } }, "itemAsins": { "type": "array", "items": { "type": "string" } }, "itemQueries": { "type": "array", "items": { "type": "string" } }, "marketplace": { "type": "string", "description": "Amazon storefront domain or id, e.g. amazon.se, amazon.com, us, se" }, "itemKeywords": { "type": "array", "items": { "type": "string" } } } }arguments 47 linesadd_registry_item unknown never probed
Add an item to an existing baby registry / wishlist. Prefer asin for tagged /dp/ links on amazon.se. Requires editToken, marketplace, locale.
{ "type": "object", "required": [ "id", "editToken", "marketplace", "locale" ], "properties": { "id": { "type": "string", "description": "Registry id" }, "url": { "type": "string" }, "asin": { "type": "string" }, "name": { "type": "string", "description": "Alias for title" }, "emoji": { "type": "string" }, "notes": { "type": "string" }, "title": { "type": "string" }, "locale": { "type": "string", "description": "End-user locale, e.g. en, en-US, sv-SE, de-DE" }, "editToken": { "type": "string" }, "marketplace": { "type": "string", "description": "Amazon storefront domain or id, e.g. amazon.se, amazon.com, us, se" }, "searchKeywords": { "type": "string" } } }arguments 48 linessearch_catalog unknown 2h ago
Search the curated baby registry catalog (100+ amazon.se essentials: sleep, feeding, diapering, gear, clothing, safety, bath, play). Returns products with asin + buyUrl. Use to pick items when building a shopping list / registry. Requires marketplace + locale.
{ "type": "object", "required": [ "marketplace", "locale" ], "properties": { "q": { "type": "string", "description": "Optional text filter (name/blurb/keywords)" }, "limit": { "type": "integer", "default": 24 }, "locale": { "type": "string", "description": "End-user locale, e.g. en, en-US, sv-SE, de-DE" }, "offset": { "type": "integer", "default": 0 }, "ageBand": { "type": "string", "description": "expecting | 0-3m | 3-6m | 6-12m | 12-24m | toddler" }, "interest": { "type": "string", "description": "sleep | feeding | diapering | gear | clothing | safety | play | bath" }, "marketplace": { "type": "string", "description": "Amazon storefront domain or id, e.g. amazon.se, amazon.com, us, se" } } }arguments 37 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 iddc55c2aa222ea160.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dc55c2aa222ea160/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dc55c2aa222ea160?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.