# Swatch Ledger (remote · swatch-ledger.pages.dev)

Fabric shrinkage from a swatch wash test, and how much fabric to buy before washing.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `swatch-ledger.pages.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/keith-cy-swatch-ledger-mcp/swatch-ledger.md), [page](https://verifymcp.io/servers/keith-cy-swatch-ledger-mcp/swatch-ledger)

## Channel facts

- Endpoint: `https://swatch-ledger.pages.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http keith-cy-swatch-ledger-mcp 'https://swatch-ledger.pages.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "keith-cy-swatch-ledger-mcp": {
      "url": "https://swatch-ledger.pages.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "keith-cy-swatch-ledger-mcp": {
      "type": "http",
      "url": "https://swatch-ledger.pages.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.keith-cy-swatch-ledger-mcp]
url = "https://swatch-ledger.pages.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "keith-cy-swatch-ledger-mcp": {
      "type": "remote",
      "url": "https://swatch-ledger.pages.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add keith-cy-swatch-ledger-mcp --url 'https://swatch-ledger.pages.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  keith-cy-swatch-ledger-mcp:
    url: "https://swatch-ledger.pages.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "keith-cy-swatch-ledger-mcp": {
      "Transport": "http",
      "Url": "https://swatch-ledger.pages.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add keith-cy-swatch-ledger-mcp -t streamable-http -u 'https://swatch-ledger.pages.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "keith-cy-swatch-ledger-mcp": {
      "type": "http",
      "url": "https://swatch-ledger.pages.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 74, +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.

### 2026-11-02 (score 73, +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.

### 2026-10-31 (score 72, +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.

### 2026-10-29 (score 71, +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.

### 2026-10-27 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 69)

First indexed and scored.

## MCP tools (2)

### `measure_fabric_shrinkage` (~180 tokens)

Measure fabric shrinkage

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.

Input parameters:

- `length_after` (number, required): The same marked length after washing and drying.
- `length_before` (number, required): 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, required): The same marked width after washing and drying.
- `width_before` (number, required): Marked width before washing (across the fabric), greater than 0.

### `plan_fabric_length` (~222 tokens)

Plan fabric length to buy

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.

Input parameters:

- `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, required): 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, required): Length needed after washing (check the pattern layout), greater than 0.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/keith-cy-swatch-ledger-mcp/swatch-ledger#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 69

## Common questions

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

## Links

- Remote endpoint: https://swatch-ledger.pages.dev/mcp
- Website: https://swatch-ledger.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/keith-cy-swatch-ledger-mcp/swatch-ledger.xml
- Changelog JSON feed: https://verifymcp.io/servers/keith-cy-swatch-ledger-mcp/swatch-ledger.json
- HTML version of this page: https://verifymcp.io/servers/keith-cy-swatch-ledger-mcp/swatch-ledger