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

jewelry-by-sweet-pea

https://chat.jewelrybysweetpea.com

Registry code: 0511f60b37c38b96

api record

Live search of 100,000+ fine jewelry products, prices and store policies. Read-only, no auth.

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

endpoint
https://chat.jewelrybysweetpea.com/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 jewelry-by-sweet-pea live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is jewelry-by-sweet-pea free to use?
Yes — the hub reached it with no key and no payment.
What tools does jewelry-by-sweet-pea have?
5 tools: search_products, get_product, list_size_variants, find_compatible_chains, get_store_policies.
Is jewelry-by-sweet-pea 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.6%

90 days 99.7%· all time 99.7%

latency
151ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 396 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • search fine jewelry products
  • get product price and availability
  • find compatible chains for a pendant
  • get store policies
takes → gives
text → data
tools
5 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 5 tools
1 open 4 never probed 1 of 5 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.

  • get_store_policies reads open 1h ago

    Shipping (free US), returns (free 30-day), warranty, resizing, payment, and contact details for Jewelry by Sweet Pea.

    mcp-tool

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

    Live search of 100,000+ fine-jewelry products (gold, sterling silver, NCAA/collegiate LogoArt). Returns name, SKU, live price, availability, product URL, and image. Best queries are short and specific (e.g. 'alabama pendant', '14k rope chain 20 inch').

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "Search terms (product type, school/team, metal, style)."
        },
        "max_results": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "Max products to return (default 6)."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • get_product reads unknown 15h ago

    Fetch one product's live details (price, availability, sizes/variants, URL) by its SKU.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "sku"
      ],
      "properties": {
        "sku": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2,
          "description": "The product SKU, e.g. GP016MIS-18."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • list_size_variants reads unknown 1h ago

    For a ring, chain, bracelet or anklet SKU, lists the sibling products that are the same piece in other sizes (ring sizes) or lengths (inches), each with its own SKU and URL. Empty when the piece comes in one size.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "sku"
      ],
      "properties": {
        "sku": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2,
          "description": "A SKU such as WCF040-5 (ring size 5) or BOX100-14 (14 inch chain)."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • find_compatible_chains reads unknown 15h ago

    For a pendant or charm SKU, returns chains whose width fits the pendant's bail (same metal family, sensible width and price), plus other pieces the store pairs with it (same school/team or same collection). Use get_product on a returned name/URL for live price and stock.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "sku"
      ],
      "properties": {
        "sku": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2,
          "description": "The pendant/charm SKU, e.g. K4324 or 4Y001CU."
        }
      },
      "additionalProperties": false
    }
    arguments 16 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 0511f60b37c38b96.

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

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.