_ registry / mcp streamable-http · checked 1h ago

planbeforeyoudie-facts

https://planbeforeyoudie.app

Registry code: b2a9e3b2a7d091de

api record

Read-only facts for getting a family ready if someone gets sick or dies. Every fact carries its official source and the date it was checked. Quote the source and link the guide page. This is general information, not legal advice. It never recommends a Medicare plan, insurance, or investment.

endpoint
https://planbeforeyoudie.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is planbeforeyoudie-facts live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is planbeforeyoudie-facts free to use?
Yes — the hub reached it with no key and no payment.
What tools does planbeforeyoudie-facts have?
8 tools: search_facts, get_form, list_guides, state_rules, inherited_ira_rule, after_death_deadlines, agency_permissions, readiness_checklist.
Is planbeforeyoudie-facts safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
210ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • readiness_checklist open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_facts unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Plain words, like \"medicare form for family\" or \"social security representative payee\""
    }
  }
}
    arguments 12 lines
  • get_form unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • list_guides unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • state_rules unknown never probed

    Return the complete published state row, conditions and source passages. This reference does not decide eligibility or an individual legal result.

    mcp-tool

    {
  "type": "object",
  "required": [
    "state",
    "topic"
  ],
  "properties": {
    "state": {
      "enum": [
        "AK",
        "AL",
        "AR",
        "AZ",
        "CA",
        "CO",
        "CT",
        "DC",
        "DE",
        "FL",
        "GA",
        "HI",
        "IA",
        "ID",
        "IL",
        "IN",
        "KS",
        "KY",
        "LA",
        "MA",
        "MD",
        "ME",
        "MI",
        "MN",
        "MO",
        "MS",
        "MT",
        "NC",
        "ND",
        "NE",
        "NH",
        "NJ",
        "NM",
        "NV",
        "NY",
        "OH",
        "OK",
        "OR",
        "PA",
        "RI",
        "SC",
        "SD",
        "TN",
        "TX",
        "UT",
        "VA",
        "VT",
        "WA",
        "WI",
        "WV",
        "WY"
      ],
      "type": "string",
      "description": "U.S. state or District of Columbia"
    },
    "topic": {
      "enum": [
        "death_certificates",
        "small_estate",
        "estate_tax",
        "unclaimed_money",
        "advance_directive_forms",
        "caregiver_programs"
      ],
      "type": "string",
      "description": "Published reference topic"
    }
  },
  "additionalProperties": false
}
    arguments 79 lines
  • inherited_ira_rule unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "account_type"
  ],
  "properties": {
    "arrangement": {
      "enum": [
        "sole_direct",
        "multiple",
        "entity",
        "successor",
        "unsure"
      ],
      "type": "string",
      "description": "How is the inherited account held?"
    },
    "account_type": {
      "enum": [
        "traditional",
        "roth",
        "employer"
      ],
      "type": "string",
      "description": "What type of account is it?"
    },
    "date_of_death": {
      "type": "string",
      "format": "date",
      "description": "Owner's date of death"
    },
    "child_under_21": {
      "enum": [
        "yes",
        "no",
        "unsure"
      ],
      "type": "string",
      "description": "Was the owner's child under 21 at death?"
    },
    "existing_method": {
      "enum": [
        "life_expectancy",
        "ten_year",
        "unsure"
      ],
      "type": "string",
      "description": "Which existing method did the custodian confirm?"
    },
    "owner_birth_year": {
      "type": "integer",
      "maximum": 2026,
      "minimum": 1900,
      "description": "Owner's birth year"
    },
    "beneficiary_category": {
      "enum": [
        "spouse",
        "child",
        "disabled",
        "chronically_ill",
        "within_ten",
        "other",
        "estate_trust_charity"
      ],
      "type": "string",
      "description": "Which beneficiary category applied at death?"
    },
    "beneficiary_birth_year": {
      "type": "integer",
      "maximum": 2026,
      "minimum": 1900,
      "description": "Beneficiary's birth year"
    },
    "exact_ten_year_age_gap": {
      "enum": [
        "yes",
        "no",
        "unsure"
      ],
      "type": "string",
      "description": "Do exact birth dates confirm the ten-year category?"
    },
    "previous_dec31_balance": {
      "type": "string",
      "pattern": "^(0|[1-9][0-9]*)(\\.[0-9]{1,2})?$",
      "description": "Balance on December 31 before this year. Optional statement balance in dollars and cents"
    },
    "required_beginning_date": {
      "enum": [
        "before",
        "on_after",
        "unsure"
      ],
      "type": "string",
      "description": "What did the custodian confirm about the beginning date?"
    },
    "death_year_withdrawal_completed": {
      "enum": [
        "yes",
        "no",
        "unsure"
      ],
      "type": "string",
      "description": "Did the owner complete the death-year withdrawal?"
    }
  },
  "additionalProperties": false
}
    arguments 109 lines
  • after_death_deadlines unknown 1h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "date_of_death",
    "state",
    "will",
    "surviving_spouse",
    "executor_started",
    "assets"
  ],
  "properties": {
    "will": {
      "enum": [
        "yes",
        "no",
        "unsure"
      ],
      "type": "string",
      "description": "Whether a will is known"
    },
    "state": {
      "enum": [
        "AK",
        "AL",
        "AR",
        "AZ",
        "CA",
        "CO",
        "CT",
        "DC",
        "DE",
        "FL",
        "GA",
        "HI",
        "IA",
        "ID",
        "IL",
        "IN",
        "KS",
        "KY",
        "LA",
        "MA",
        "MD",
        "ME",
        "MI",
        "MN",
        "MO",
        "MS",
        "MT",
        "NC",
        "ND",
        "NE",
        "NH",
        "NJ",
        "NM",
        "NV",
        "NY",
        "OH",
        "OK",
        "OR",
        "PA",
        "RI",
        "SC",
        "SD",
        "TN",
        "TX",
        "UT",
        "VA",
        "VT",
        "WA",
        "WI",
        "WV",
        "WY"
      ],
      "type": "string",
      "description": "State where the person lived"
    },
    "assets": {
      "type": "array",
      "items": {
        "enum": [
          "retirement",
          "home",
          "sole",
          "insurance",
          "ssa",
          "pension",
          "vehicle"
        ],
        "type": "string",
        "description": "Relevant asset category"
      },
      "uniqueItems": true
    },
    "date_of_death": {
      "type": "string",
      "format": "date"
    },
    "executor_started": {
      "enum": [
        "yes",
        "no",
        "unsure"
      ],
      "type": "string",
      "description": "Whether someone has started acting as executor. This does not establish authority"
    },
    "surviving_spouse": {
      "enum": [
        "yes",
        "no"
      ],
      "type": "string",
      "description": "Whether there is a surviving spouse"
    }
  },
  "additionalProperties": false
}
    arguments 118 lines
  • agency_permissions unknown 1h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "agency",
    "situation"
  ],
  "properties": {
    "agency": {
      "enum": [
        "ssa",
        "rrb",
        "irs",
        "medicare",
        "va",
        "opm",
        "usps",
        "tsp"
      ],
      "type": "string",
      "description": "Agency"
    },
    "situation": {
      "enum": [
        "well",
        "capacity",
        "death"
      ],
      "type": "string",
      "description": "Reading focus. All conditions remain in the returned rows"
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b2a9e3b2a7d091de.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b2a9e3b2a7d091de/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b2a9e3b2a7d091de/badge.svg)](https://brick.blue/agent/b2a9e3b2a7d091de?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.