Skip to content

WearableDocs MCP server

com.wearabledocs/wearabledocswearabledocs.comstreamable-httpv1.0.3Scanned

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

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 4
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the WearableDocs MCP server can do

The WearableDocs MCP server is published by wearabledocs.com, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

4 tools read private data (search_site, get_faq, get_products and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Only reads 6Show 6 read-only tools
  • get_faqEvery question answered on the WearableDocs FAQ and the Medical & Legal FAQ, in the words the site answers them in.Reads private dataNo findings

    Why it is in this group

    • The name "get_faq" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read the FAQ
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_pricingEvery 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…Reads private dataNo findings

    Why it is in this group

    • The name "get_pricing" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get prices
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_productsThe WearableDocs product line: the things a record code can be carried on.Reads private dataNo findings

    Why it is in this group

    • The name "get_products" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List products
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_stateWhat one US jurisdiction requires to refuse anatomical gift.No findings

    Why it is in this group

    • The name "get_state" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get one state
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_statesList every US state and the District of Columbia, with the statute that governs a refusal of anatomical gift there.No findings

    Why it is in this group

    • The name "list_states" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List jurisdictions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_siteFind which WearableDocs page answers a question, by keyword.Reads private dataNo findings

    Why it is in this group

    • The name "search_site" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the site
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http wearabledocs https://wearabledocs.com/mcp
claude mcp add --transport http wearabledocs https://wearabledocs.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wearabledocs__list_states",
      "mcp__wearabledocs__get_state",
      "mcp__wearabledocs__search_site",
      "mcp__wearabledocs__get_faq",
      "mcp__wearabledocs__get_products",
      "mcp__wearabledocs__get_pricing"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wearabledocs. Review it before you use it.

Capability tags behind 4 rules
  • mcp__wearabledocs__search_site private-data
  • mcp__wearabledocs__get_faq private-data
  • mcp__wearabledocs__get_products private-data
  • mcp__wearabledocs__get_pricing private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.wearabledocs/wearabledocs/verify?hash=50ab5e44043dac67a0bc8e4357615e69827250ed95f316d851aae6c15568af2c" | jq -e '.changed == false'

Pinned hash 50ab5e44043d, from Nov 14, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.wearabledocs/wearabledocs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.wearabledocs/wearabledocs
[![Anlyon Radar](https://radar.anlyon.com/badge/com.wearabledocs/wearabledocs.svg)](https://radar.anlyon.com/servers/com.wearabledocs/wearabledocs)

Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.

WearableDocs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the WearableDocs MCP server safe?

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the WearableDocs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the WearableDocs MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the WearableDocs MCP server have?

6 tools: 6 read. list_states, get_state, search_site, get_faq, get_products and get_pricing.

Does the WearableDocs MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the WearableDocs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the WearableDocs MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.