Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WearableDocs

REMOTE · WEARABLEDOCS.COM

Refusal of anatomical gift in 50 states and DC, plus the WearableDocs FAQ, products, prices, search.

Available components

0 this week 87 Trust /100

Last scanned (20 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 Security83
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 968 tokens (~161/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Sept 26 0
    • Authorization: unverified → partial ▲ security
    • Tool “get_faq” rewrote its description, which is the text the model reads security
    • Tool “get_state” rewrote its description, which is the text the model reads security
    • Tool “search_site” rewrote its description, which is the text the model reads security
    • Schema quality: 129 → 161 ▼ functional
    • Server version: 1.0.2 → 1.0.3 functional
    • Tool “get_faq” changed its title: Read the FAQ cosmetic
    • Tool “get_pricing” changed its title: Get prices cosmetic
    • Tool “get_products” changed its title: List products cosmetic
    • Tool “get_state” changed its title: Get one state cosmetic
    • Tool “list_states” changed its title: List jurisdictions cosmetic
    • Tool “search_site” changed its title: Search the site cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 15 Sept 26 0
    • 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 security
    • Schema quality: pass → fail ▼ functional
    • Server version: 1.0.0 → 1.0.2 functional
Diagnostics

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 21 Nov 2026 · Probed https://wearabledocs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wearabledocs.com CN=WE1,O=Google Trust Services,C=US 4 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 6aa2043776353c641361190134b9e965
SANs: wearabledocs.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of wearabledocs.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
wearabledocs.com. DS published 2371 13 Verified
wearabledocs.com. Verified address RRset verified with the apex keys
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
strict-transport-security max-age=31536000
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://wearabledocs.com/mcp Verified 200
http (plaintext) http://wearabledocs.com/mcp HTTPS enforced 301 https://wearabledocs.com/mcp
MCP tools · 6 exposed · ~915 tokens

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 →

Tool Tokens
get_faq ~149

Every question answered on the WearableDocs FAQ and the Medical & Legal FAQ, in the words the site answers them in. Returns `questions`, each with the `question`, its full `answer` and the `page` it appears on. The whole set comes back in one call and there is nothing to filter by, so pick the question closest to the one asked from this list rather than calling again. 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, get_state when the question names a jurisdiction, and search_site for a topic these questions do not reach.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~89

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_products ~154

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_state ~200

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) are still on the 1968 act and their statutes prescribe no formalities for a refusal, so their facts report none and their summaries explain what gives a refusal effect there instead: do not report a witness or notary requirement for those four. An unknown state is an error listing every code it accepts.

NameTypeReqDescription
statestringyesA state name or two-letter postal code, for example "Texas" or "TX".

No output schema declared.

No examples provided.

list_states ~50

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_site ~273

Find which WearableDocs page answers a question, by keyword. Returns `matches`, best first, each with the page `url`, a `markdown` address for a clean copy of the page, its `title`, its section `headings` and a one-sentence `excerpt`. The matches point to pages; they do not contain the answer, so fetch the `markdown` copy and read it before answering. No match is an empty list, not an error: try again with fewer, plainer words. Use this for anything about the product, the record page, evidence, engraving, the health and rights articles or the comparison pages. For what one state requires use get_state, for a general question about how refusals work use get_faq, and for a price use get_pricing.

NameTypeReqDescription
limitinteger–How many pages to return, best match first. Defaults to 5, and anything above 20 is capped rather than refused.
querystringyesThe 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…

No output schema declared.

No examples provided.

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.

remote · wearabledocs.com

# add to Claude Code
claude mcp add --transport http com-wearabledocs-wearabledocs 'https://wearabledocs.com/mcp'
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 50 states and DC, plus the WearableDocs FAQ, products, prices, search. This page covers its hosted endpoint (https://wearabledocs.com/mcp).

Is the WearableDocs MCP server safe to use?

WearableDocs scores 87 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 915 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the WearableDocs MCP server?

VerifyMCP ran 13 checks on WearableDocs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.