swatch-ledger
https://swatch-ledger.pages.dev
Registry code: bd899f696077a082
Swatch Ledger (swatch-ledger.pages.dev) is a free fabric shrinkage and yardage calculator for sewing. measure_fabric_shrinkage turns before-and-after swatch measurements (length along the selvedge and width across the fabric, after washing and drying) into length, width and area shrinkage or growth. plan_fabric_length works out how much fabric to buy so that a usable length remains after washing, from a measured lengthwise shrinkage rate, with optional extra length and rounding up to the shop’s selling increment.
They fit when a user asks how much a fabric shrank in a wash test, or how much…
- endpoint
- https://swatch-ledger.pages.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 swatch-ledger live?
- Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
- Is swatch-ledger free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does swatch-ledger have?
- 2 tools: measure_fabric_shrinkage, plan_fabric_length.
- Is swatch-ledger 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 2 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.
measure_fabric_shrinkage unknown 52m ago
Calculates fabric shrinkage (or growth) from a swatch measured before and after washing and drying: length change along the selvedge, width change across the fabric, and the change in area. Use the same marked distances before and after, in one unit (cm or inches). Positive percentages are shrinkage, negative are growth.
{ "type": "object", "required": [ "length_before", "length_after", "width_before", "width_after" ], "properties": { "unit": { "enum": [ "cm", "in" ], "type": "string", "description": "Unit of the four measurements (only used to label the answer). Default cm." }, "width_after": { "type": "number", "description": "The same marked width after washing and drying.", "exclusiveMinimum": 0 }, "length_after": { "type": "number", "description": "The same marked length after washing and drying.", "exclusiveMinimum": 0 }, "width_before": { "type": "number", "description": "Marked width before washing (across the fabric), greater than 0.", "exclusiveMinimum": 0 }, "length_before": { "type": "number", "description": "Marked length before washing (along the selvedge), greater than 0.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 40 linesplan_fabric_length unknown 52m ago
Works out how much fabric to buy before washing so that the usable length needed remains afterwards: required length = (usable length + extra) ÷ (1 − lengthwise shrinkage), then rounded up to the shop’s selling increment. Works in metres or yards (any one unit). A negative shrinkage rate means growth.
{ "type": "object", "required": [ "usable_length", "shrinkage_percent" ], "properties": { "unit": { "enum": [ "m", "yd" ], "type": "string", "description": "Unit of the lengths (only used to label the answer). Default m." }, "extra_length": { "type": "number", "minimum": 0, "description": "Optional extra usable length after washing (default 0). Do not count an allowance the pattern already includes." }, "usable_length": { "type": "number", "description": "Length needed after washing (check the pattern layout), greater than 0.", "exclusiveMinimum": 0 }, "shop_increment": { "type": "number", "minimum": 0, "description": "The shop’s selling increment to round up to, e.g. 0.25 for quarter metres or 0.125 for eighth yards. 0 for no rounding (default 0)." }, "shrinkage_percent": { "type": "number", "minimum": -100, "description": "Measured lengthwise shrinkage in percent, e.g. 5 for 5%. Negative means growth.", "exclusiveMaximum": 100 } }, "additionalProperties": false }arguments 39 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 idbd899f696077a082.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/bd899f696077a082/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/bd899f696077a082?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.