Swatch Ledger
REMOTE · SWATCH-LEDGER.PAGES.DEV
Fabric shrinkage from a swatch wash test, and how much fabric to buy before washing.
Available components
Last scanned (50 minutes ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 632 tokens (~316/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://swatch-ledger.pages.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=swatch-ledger.pages.dev | CN=YE2,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 66df82712767b2b1b72bb8a3ff05095c96e |
| SANs: *.swatch-ledger.pages.dev, swatch-ledger.pages.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of swatch-ledger.pages.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pages.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://swatch-ledger.pages.dev/mcp | Verified | 200 | |
| http (plaintext) | http://swatch-ledger.pages.dev/mcp | HTTPS enforced | 301 | https://swatch-ledger.pages.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
measure_fabric_shrinkage Measure fabric shrinkage ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| length_after | number | yes | The same marked length after washing and drying. |
| length_before | number | yes | Marked length before washing (along the selvedge), greater than 0. |
| unit | string | – | Unit of the four measurements (only used to label the answer). Default cm. |
| width_after | number | yes | The same marked width after washing and drying. |
| width_before | number | yes | Marked width before washing (across the fabric), greater than 0. |
No output schema declared.
No examples provided.
plan_fabric_length Plan fabric length to buy ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| extra_length | number | – | Optional extra usable length after washing (default 0). Do not count an allowance the pattern already includes. |
| shop_increment | number | – | 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 | number | yes | Measured lengthwise shrinkage in percent, e.g. 5 for 5%. Negative means growth. |
| unit | string | – | Unit of the lengths (only used to label the answer). Default m. |
| usable_length | number | yes | Length needed after washing (check the pattern layout), greater than 0. |
No output schema declared.
No examples provided.
How do I install the Swatch Ledger MCP server?
Swatch Ledger is a hosted endpoint at https://swatch-ledger.pages.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · swatch-ledger.pages.dev
claude mcp add --transport http keith-cy-swatch-ledger-mcp 'https://swatch-ledger.pages.dev/mcp'
What is the Swatch Ledger MCP server?
Swatch Ledger is an MCP server listed in the public MCP registry as io.github.Keith-CY/swatch-ledger-mcp. Fabric shrinkage from a swatch wash test, and how much fabric to buy before washing. This page covers its hosted endpoint (https://swatch-ledger.pages.dev/mcp).
Is the Swatch Ledger MCP server safe to use?
Swatch Ledger scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Swatch Ledger MCP server expose?
Swatch Ledger exposes 2 tools: measure_fabric_shrinkage, plan_fabric_length. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Does the Swatch Ledger MCP server require authentication?
No. We connected to Swatch Ledger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Swatch Ledger MCP server still maintained?
Swatch Ledger is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.