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

mamachoice

https://mamachoice-mcp.ohadf1976.workers.dev

Registry code: a3bee09c4311d378

api record

MamaChoice (אמא בוחרת) is an Israeli site of Hebrew buying guides for baby products and parents. search_guides finds guides by topic, get_guide returns a guide's products (₪, delivery to Israel) and FAQ, search_baby_products runs a live AliExpress baby-product search for Israel.

endpoint
https://mamachoice-mcp.ohadf1976.workers.dev/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 mamachoice live?
Yes — it answered the hub's last check (checked 39m ago). It answered 100% of checks over the last 30 days.
Is mamachoice free to use?
Yes — the hub reached it with no key and no payment.
What tools does mamachoice have?
3 tools: search_guides, get_guide, search_baby_products.
Is mamachoice 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
351ms

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.

  • search_guides unknown 39m ago

    Find MamaChoice's Hebrew buying guides for baby products and parents in Israel (equipment checklists, strollers and carriers, sleep, feeding, toys by age, safety, travel, gifts, AliExpress import VAT/customs). Accepts Hebrew or English. Returns matching guides with title, link, summary and a few of their products.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Topic in Hebrew or English, e.g. \"תיק החתלה\", \"כוס מעבר\", \"toys for a 1 year old\"."
        },
        "max_results": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "How many guides to return (1-10). Default 5."
        }
      }
    }
    arguments 18 lines
  • get_guide unknown 39m ago

    Return one MamaChoice guide in full: its products (name, price in ₪, link to the AliExpress listing with delivery to Israel) and its frequently asked questions with answers. Use the slug or URL from search_guides.

    mcp-tool

    {
      "type": "object",
      "required": [
        "guide"
      ],
      "properties": {
        "guide": {
          "type": "string",
          "description": "Guide slug (e.g. \"tikey-hachatala-lehorim\") or its full URL."
        }
      }
    }
    arguments 12 lines
  • search_baby_products unknown 39m ago

    Live search of AliExpress baby and parenting products with delivery to Israel and prices in ₪, through the OneFindMe engine. Accepts Hebrew or English. Use when no guide covers the product.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "What the parent is looking for, e.g. \"שמיכה לעגלה\" or \"baby bath thermometer\"."
        },
        "max_results": {
          "type": "integer",
          "maximum": 15,
          "minimum": 1,
          "description": "How many products to return (1-15). Default 8."
        }
      }
    }
    arguments 18 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 a3bee09c4311d378.

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