# WearableDocs (remote · wearabledocs.com)

Refusal of anatomical gift in all 51 US jurisdictions, plus the WearableDocs FAQ, prices and search.

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

## Components

- remote · `wearabledocs.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-wearabledocs-wearabledocs/wearabledocs.md), [page](https://verifymcp.io/servers/com-wearabledocs-wearabledocs/wearabledocs)

## Channel facts

- Endpoint: `https://wearabledocs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 774 tokens (~129/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the WearableDocs MCP server?

WearableDocs is a hosted endpoint at https://wearabledocs.com/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 com-wearabledocs-wearabledocs 'https://wearabledocs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wearabledocs-wearabledocs": {
      "url": "https://wearabledocs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wearabledocs-wearabledocs": {
      "type": "http",
      "url": "https://wearabledocs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wearabledocs-wearabledocs]
url = "https://wearabledocs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wearabledocs-wearabledocs": {
      "type": "remote",
      "url": "https://wearabledocs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wearabledocs-wearabledocs --url 'https://wearabledocs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wearabledocs-wearabledocs:
    url: "https://wearabledocs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wearabledocs-wearabledocs": {
      "Transport": "http",
      "Url": "https://wearabledocs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wearabledocs-wearabledocs -t streamable-http -u 'https://wearabledocs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-wearabledocs-wearabledocs": {
      "type": "http",
      "url": "https://wearabledocs.com/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-09-27 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 70, +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-09-16 (score 69, +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-09-15 (score 68, 0)

- [security] Tool “get_pricing” rewrote its description, which is the text the model reads
- [security] Tool “get_products” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.0.0 → 1.0.2

### 2026-09-14 (score 68, +1)

- [security] Tool “get_products” rewrote its description, which is the text the model reads
- [security] Tool “get_state” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 91 → 113
- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `list_states` (~50 tokens)

List every US state and the District of Columbia, with the statute that governs a refusal of anatomical gift there. Use this to find which jurisdictions are covered or to get the exact name to pass to get_state.

### `get_state` (~188 tokens)

What one US jurisdiction requires to refuse anatomical gift. Use this for any question naming a state; use get_faq for a general one. Returns the statute citation, a plain-language summary, and a facts list: which act the state enacted, whether witnesses are needed when you sign it yourself and when someone signs at your direction, whether a notary is required, and what an unrevoked refusal bars. Covers all 50 states and the District of Columbia. Four of them (Delaware, Florida, New York, Pennsylvania) enact no refusal provision at all, so their facts describe the nearest provisions their act does have rather than a refusal rule: do not report a witness or notary requirement for those four. An unknown state is an error listing every code it accepts.

Input parameters:

- `state` (string, required): A state name or two-letter postal code, for example "Texas" or "TX".

### `search_site` (~160 tokens)

Find which WearableDocs page answers a question. Returns page titles, headings and the address of a clean Markdown copy to read. Use this before answering anything about the product, the record page, evidence, engraving, pricing or health and rights.

Input parameters:

- `limit` (integer): How many pages to return, best match first. Defaults to 5, and anything above 20 is capped rather than refused.
- `query` (string, required): The words to match. This is keyword search, not semantic: words are stemmed and looked for in page titles, addresses, headings and excerpts, so a few plain nouns ("engraving", "brain death", "Texas r…

### `get_faq` (~80 tokens)

Every question answered on the WearableDocs FAQ and the Medical & Legal FAQ, in the words they are answered in. Covers enforceability, refusing vaccines and blood, brain death, organ procurement practice, and what happens if a refusal is ignored. Use this for a general question about how refusals work, and get_state when the question names a jurisdiction.

### `get_products` (~154 tokens)

The WearableDocs product line: the things a record code can be carried on. A printed wallet card, and four laser engraved stainless steel wearables — a tag pendant, a coin pendant, a coin bracelet and a bangle bracelet. Returns a key, name, description, price, a `purchasable` flag and a `url` for each: the product page in the shop where it is ordered. Read `purchasable` rather than assuming in either direction, and send someone who wants to buy one to its `url`. Use this to answer what a WearableDocs code can be worn on, or which shape suits someone; use get_pricing for the figures alone and for the subscription.

### `get_pricing` (~89 tokens)

Every WearableDocs price: the yearly subscription for the first person and for each additional person on a household plan, and the one-time cost of each wearable and of the printed wallet card. Figures are US cents and dollars, and are what the checkout actually charges. Only settled prices appear here — never quote a price for anything this tool does not return, and never infer one from a product name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wearabledocs-wearabledocs/wearabledocs#diagnostics

## Score history

- 2026-09-27: 74
- 2026-09-26: 73
- 2026-09-25: 73
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 71
- 2026-09-21: 71
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67

## Common questions

### What is the WearableDocs MCP server?

WearableDocs is an MCP server listed in the public MCP registry as com.wearabledocs/wearabledocs. Refusal of anatomical gift in all 51 US jurisdictions, plus the WearableDocs FAQ, prices and search. This page covers its hosted endpoint (https://wearabledocs.com/mcp).

### Is the WearableDocs MCP server safe to use?

WearableDocs 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 WearableDocs MCP server expose?

WearableDocs exposes 6 tools: list_states, get_state, search_site, get_faq, get_products, get_pricing. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.

### Does the WearableDocs MCP server require authentication?

No. We connected to WearableDocs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WearableDocs MCP server still maintained?

WearableDocs is still listed as active in the MCP registry. We last reached this channel on 27 September 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://wearabledocs.com/mcp
- Website: https://wearabledocs.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-wearabledocs-wearabledocs/wearabledocs.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wearabledocs-wearabledocs/wearabledocs.json
- HTML version of this page: https://verifymcp.io/servers/com-wearabledocs-wearabledocs/wearabledocs