Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
WearableDocs is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Refusal of anatomical gift in 50 states and DC, plus the WearableDocs FAQ, products, prices, search.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http wearabledocs-mcp https://wearabledocs.com/mcp
# 2 — ask your agent for something these tools do
# list_states, get_state, search_site and 3 more
WearableDocs costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WEAll 1 server
wearabledocs1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http wearabledocs-mcp https://wearabledocs.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | A state name or two-letter postal code, for example "Texas" or "TX". |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 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 re |
| limit | integer | no | How many pages to return, best match first. Defaults to 5, and anything above 20 is capped rather than refused. |
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, refusi
No parameter schema on file.
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 eit
No parameter schema on file.
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
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install WearableDocs or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.3.
1.0.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish WearableDocs can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.