_ registry / mcp + a2a JSONRPC · checked 53m ago

custom-blinds-shop

https://shop.customblinds.co.za

Registry code: 2dc169dbea8feda1

api record

Custom Blinds Shutters & Awnings shop: made-to-measure blinds in South Africa. All prices are ZAR, VAT included. Flow: search_catalog or lookup_catalog, get_product, get_price, configure_product (validates an exact colour; use check_colour_stock for a named colour), create_cart, create_checkout, complete_checkout. Browsing, pricing, cart and checkout are open; submit_enquiry and create_order need a partner Bearer key. create_checkout creates a real unpaid order: confirm product, size, colour, total and the customer's real name, email, mobile and delivery address before calling it. Test or…

endpoint
https://shop.customblinds.co.za/
door code
e86f8c1ab53357d8
protocol
JSONRPC ·0.2
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 custom-blinds-shop live?
Yes — it answered the hub's last check (checked 53m ago). It answered 99% of checks over the last 30 days.
Is custom-blinds-shop free to use?
Yes — the hub reached it with no key and no payment.
What tools does custom-blinds-shop have?
3 tools: product_discovery, instant_pricing, checkout.
Is custom-blinds-shop 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
98.9%

90 days 99.2%· all time 99.6%

latency
117ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 733 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • search custom blinds and shutters
  • get an exact price for a blind size
  • create a cart and checkout
  • get a payment link for an order
  • check order status
takes → gives
text, data, payments → data
_ 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 from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ 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.

  • skill-0 unknown never probed

    Search the product catalogue by type, colour and dimensions

  • skill-1 unknown never probed

    Exact ZAR price for a product at a given width and drop (VAT included)

  • skill-2 unknown never probed

    Cart and checkout flow ending in a Yoco card or Ozow EFT payment link

_ try it over a2a 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 2dc169dbea8feda1.

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

_ also on customblinds.co.za 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.