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.

Plan Before You Die facts

REMOTE · PLANBEFOREYOUDIE.APP

Checked US family-readiness facts with official sources: forms, state rules and deadlines.

+4 this week 78 Trust /100

Last scanned (6 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 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 Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 853 tokens (~106/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 1 Nov 26 +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.

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1
    • Tool “state_rules” rewrote its description, which is the text the model reads security
    • Schema quality: 91 → 102 ▼ functional
  • 26 Oct 26 +1

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

  • 25 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 72

    First indexed and scored.

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 5 Nov 2026 · Probed https://planbeforeyoudie.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=planbeforeyoudie.app CN=WE1,O=Google Trust Services,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 ffb73968996637b50e44943313f9711b
SANs: planbeforeyoudie.app, www.planbeforeyoudie.app, *.www.planbeforeyoudie.app
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 insecure

Validation of planbeforeyoudie.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
planbeforeyoudie.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' https://cloudflareinsights.com; form-action 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://planbeforeyoudie.app/mcp Verified 200
http (plaintext) http://planbeforeyoudie.app/mcp HTTPS enforced 301 https://planbeforeyoudie.app/mcp
MCP tools · 8 exposed · ~759 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
after_death_deadlines ~114

Return the same sourced dates and conditional review checkpoints as the public calendar. It does not establish who can act or select a form.

NameTypeReqDescription
assetsarrayyes–
date_of_deathstringyes–
executor_startedstringyesWhether someone has started acting as executor. This does not establish authority
statestringyesState where the person lived
surviving_spousestringyesWhether there is a surviving spouse
willstringyesWhether a will is known

No output schema declared.

No examples provided.

agency_permissions ~60

Return the published agency routes with forms, conditions, incapacity and death limits. The situation selects a reading focus and never grants authority.

NameTypeReqDescription
agencystringyesAgency
situationstringyesReading focus. All conditions remain in the returned rows

No output schema declared.

No examples provided.

get_form ~50

Look up an official form by code (for example CMS-10106) and get what it does in plain words, the official link, and our step-by-step guide.

NameTypeReqDescription
codestringyes–

No output schema declared.

No examples provided.

inherited_ira_rule ~249

Use the existing sourced calculator. Returns review conditions and timing. Dollar amounts require an optional prior December 31 balance. It does not choose a spouse option or an election.

NameTypeReqDescription
account_typestringyesWhat type of account is it?
arrangementstring–How is the inherited account held?
beneficiary_birth_yearinteger–Beneficiary's birth year
beneficiary_categorystring–Which beneficiary category applied at death?
child_under_21string–Was the owner's child under 21 at death?
date_of_deathstring–Owner's date of death
death_year_withdrawal_completedstring–Did the owner complete the death-year withdrawal?
exact_ten_year_age_gapstring–Do exact birth dates confirm the ten-year category?
existing_methodstring–Which existing method did the custodian confirm?
owner_birth_yearinteger–Owner's birth year
previous_dec31_balancestring–Balance on December 31 before this year. Optional statement balance in dollars and cents
required_beginning_datestring–What did the custodian confirm about the beginning date?

No output schema declared.

No examples provided.

list_guides ~27

List the free guides and tools on planbeforeyoudie.app with their short answers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

readiness_checklist ~36

The Family Readiness Standard: 25 checks a family should be able to pass if someone gets sick or dies, grouped by area.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_facts ~80

Search checked facts about getting a family ready for illness or death: Medicare permission forms, Social Security, hospital stays, unclaimed money, and more. Each result has the official source, the date checked, and a guide link.

NameTypeReqDescription
querystringyesPlain words, like "medicare form for family" or "social security representative payee"

No output schema declared.

No examples provided.

state_rules ~143

Return the complete published state row, conditions and source passages, each with its official source and the date it was checked. Topics: death_certificates (death certificates), small_estate (small estate limits), estate_tax (estate and inheritance tax), unclaimed_money (unclaimed money), advance_directive_forms (advance directive forms), caregiver_programs (paid family caregiver programs), intestacy (who inherits without a will, from each state intestacy statute). This reference does not decide eligibility, a share of an estate, or any individual legal result.

NameTypeReqDescription
statestringyesU.S. state or District of Columbia
topicstringyesPublished reference topic

No output schema declared.

No examples provided.

Install

How do I install the Plan Before You Die facts MCP server?

Plan Before You Die facts is a hosted endpoint at https://planbeforeyoudie.app/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 · planbeforeyoudie.app

# add to Claude Code
claude mcp add --transport http app-planbeforeyoudie-facts 'https://planbeforeyoudie.app/mcp'
Common questions

What is the Plan Before You Die facts MCP server?

Plan Before You Die facts is an MCP server listed in the public MCP registry as app.planbeforeyoudie/facts. Checked US family-readiness facts with official sources: forms, state rules and deadlines. This page covers its hosted endpoint (https://planbeforeyoudie.app/mcp).

Is the Plan Before You Die facts MCP server safe to use?

Plan Before You Die facts scores 78 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 Plan Before You Die facts MCP server expose?

Plan Before You Die facts exposes 8 tools: search_facts, get_form, readiness_checklist, list_guides, after_death_deadlines, and 3 more. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.

Does the Plan Before You Die facts MCP server require authentication?

No. We connected to Plan Before You Die facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Plan Before You Die facts MCP server still maintained?

Plan Before You Die facts 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.