# firenum retirement planner

> When can you retire? A FIRE plan from your numbers, graded by Monte Carlo and every year since 1872.

- name: com.firenum/fire-planner
- version: 1.4.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 83/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.firenum%2Ffire-planner
- tools: https://api.protogrid.dev/v1/servers/com.firenum%2Ffire-planner/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "fire-planner": {
      "type": "http",
      "url": "https://firenum.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 97
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-92% +updated-2d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 83/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 79 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 1 of 1 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: build_retirement_plan (idempotentHint)
- pass `tools.token_cost`: about 2,807 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 6 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 1, about 2,807 tokens to load them all
- tool set hash: bf505bb38d24260b0d0c11864449f56e
- tools last changed: 2026-10-19T07:53:53.772Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.firenum/fire-planner.svg)](https://protogrid.dev/servers/com.firenum/fire-planner)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `build_retirement_plan` changed (outputSchema)
- 2026-10-19 `build_retirement_plan` changed (description, inputSchema, outputSchema)
  - before: Use when someone asks when they can retire, if their money will last, their FIRE number (the planner shows when they'd reach it), or about Coast, Barista, Lean or Fat FIRE, and gave numbers (age, income, savings, spending, debts). Send what they gave, as said. Returns its answer and plan link. Turns what someone has said about their money into firenum's answer and their plan in firenum's Fire Planner (FIRE: Financial Independence, Retire Early). The answer is the planner's own, as their plan shows it once opened: when they can retire with their contributions, growth and inflation, graded three ways (average returns, 500 Monte Carlo simulations, every historical start year since 1872). For a FIRE number it gives the number and, once it has their age, when they would reach it. All parameters are optional: with too little to grade, `missing` says what to ask for. Reply from `answer`. Give the headline with both counts: the headline's date is the first month the money lasts on average returns, and the counts say how often that survives real market swings. When a count is under half, open with that count ("The money lasts in only N of 500 simulated markets"), never with yes, even a qualified one ("on average returns, yes", "a risky yes"): the date works on average but fails in most markets. `coast_number` is their Coast FIRE number for `coast_age` (what they would need invested today to stop saving). `coast` is the planner's own answer to stopping saving today: whether the money still lasts if they retire on the headline's date and, if not, the date that works without more saving. `assumed`, when present, is what the answer took for something they didn't say: say so in those terms. `missing` is what the planner needs before it can grade anything: ask for it and call again. To grade another retirement year, call again with `retire`. Amounts are in their currency, sums in today's money. `table` is their net worth year by year on each model, with income, spending and withdrawals, and `assumptions` is what the answer rests on (the rates, how each model works, how their numbers were read, what is not modeled): answer follow-ups from them (what they would have at 60, when the money runs out in a bad market, why a date) without calling again, and say what an answer assumes when it matters. Give them the returned url exactly as it is: it opens their quick-start with these numbers filled in, then the whole plan (stress tests, a year-by-year table, where the money goes). Without `source=agent` the planner opens it as a shared plan that saves nothing. It runs in their browser with no account, and nothing is saved until they confirm: the link then becomes a new plan, "From a link", beside any plans they have. The plan keeps the accounts, spending lines, debts, pension, Social Security and rental income sent. Salary and side income become one monthly income. Income is annual. Expenses and contributions are monthly. Amounts in whole currency units (not cents). Growth and inflation are percentages. Before retirement, any spending, debt payments and contributions that income doesn't cover are paid from savings. Without `salary` or `side_income`, and with retirement still ahead, the answer assumes an income that covers spending, contributions and debt payments until then (`assumed` says so), and the quick-start asks for it.
  - after: Use when someone asks when they can retire, if their money will last, their FIRE number (the planner shows when they'd reach it), or about Coast, Barista, Lean or Fat FIRE, and gave numbers (age, income, savings, spending, debts). Send what they gave, as said. Returns its answer and plan link. Turns what someone has said about their money into firenum's answer and their plan in firenum's Fire Planner (FIRE: Financial Independence, Retire Early). The answer is the planner's own, as their plan shows it once opened: when they can retire with their contributions, growth and inflation, graded three ways (average returns, 500 Monte Carlo simulations, every historical start year since 1872). For a FIRE number it gives the number and, once it has their age, when they would reach it. All parameters are optional: with too little to grade, `missing` says what to ask for. Reply from `answer`. Give the headline with both counts: the headline's date is the first month the money lasts on average returns, and the counts say how often that survives real market swings. When a count is under half, open with that count ("The money lasts in only N of 500 simulated markets"), never with yes, even a qualified one ("on average returns, yes", "a risky yes"): the date works on average but fails in most markets. `coast_number` is their Coast FIRE number for `coast_age` (what they would need invested today to stop saving). `coast` is the planner's own answer to stopping saving today: whether the money still lasts if they retire on the headline's date and, if not, the date that works without more saving. `assumed`, when present, is what the answer took for something they didn't say: say so in those terms. `missing` is what the planner needs before it can grade anything: ask for it and call again. To grade another retirement year, call again with `retire`. Amounts are in their currency, sums in today's money. `table` is their net worth year by year on each model, with income, spending and withdrawals, and `assumptions` is what the answer rests on (the rates, how each model works, how their numbers were read, what is not modeled): answer follow-ups from them (what they would have at 60, when the money runs out in a bad market, why a date) without calling again, and say what an answer assumes when it matters. Give them the returned url exactly as it is: it opens their quick-start with these numbers filled in, then the whole plan (stress tests, a year-by-year table, where the money goes). Without `source=agent` the planner opens it as a shared plan that saves nothing. It runs in their browser with no account, and nothing is saved until they confirm: the link then becomes a new plan, "From a link", beside any plans they have. The plan keeps the accounts, spending lines, debts, pension, Social Security and rental income sent. Salary and side income become one monthly income. Income is annual. Expenses and contributions are monthly. Amounts in whole currency units (not cents). Growth and inflation are percentages. Taxes are off by default, in any country: income is take-home pay. For someone in the US who gives income before tax, send `taxes=us` (and `state`, a partner, dependents, their Social Security statement figure and a Roth conversion strategy when they say them): the planner then computes federal, state and payroll tax every year, and the table gains each year's tax. Amounts are then dollars. Before retirement, any spending, debt payments and contributions that income doesn't cover are paid from savings. Without `salary` or `side_income`, and with retirement still ahead, the answer assumes an income that covers spending, contributions and debt payments until then (`assumed` says so), and the quick-start asks for it.

Full history: https://api.protogrid.dev/v1/servers/com.firenum%2Ffire-planner/changes

## Remotes

- https://firenum.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.9230769)

## Packages

_none_

## Tools (1)

- `build_retirement_plan`: Use when someone asks when they can retire, if their money will last, their FIRE number (the planner shows when
they'd reach it), or about Coast, Barista, Lean or Fat FIRE, and gave numbers (age, income, savings, spending,
debts). Send what they gave, as said. Returns its answer and plan link.

Turns what someone has said about their money into firenum's answer and their plan in firenum's Fire Planner
(FIRE: Financial Independence, Retire Early). The answer is the planner's own, as their plan shows it once
opened: when they can retire with their contributions, growth and inflation, graded three ways (average returns,
500 Monte Carlo simulations, every historical start year since 1872). For a FIRE number it gives the number and,
once it has their age, when they would reach it. All parameters are optional: with too little to grade,
`missing` says what to ask for.

Reply from `answer`. Give the headline with both counts: the headline's date is the first month the money lasts on
average returns, and the counts say how often that survives real market swings. When a count is under half, open
with that count ("The money lasts in only N of 500 simulated markets"), never with yes, even a qualified one ("on
average returns, yes", "a risky yes"): the date works on average but fails in most markets. `coast_number` is
their Coast FIRE number for `coast_age` (what they would need invested today to stop saving). `coast` is the
planner's own answer to stopping saving today: whether the money still lasts if they retire on the headline's date
and, if not, the date that works without more saving. `assumed`, when present, is what the answer took for
something they didn't say: say so in those terms. `missing` is what the planner needs before it can grade
anything: ask for it and call again. To grade another retirement year, call again with `retire`. Amounts are in
their currency, sums in today's money. `table` is their net worth year by year on each model, with income,
spending and withdrawals, and `assumptions` is what the answer rests on (the rates, how each model works, how
their numbers were read, what is not modeled): answer follow-ups from them (what they would have at 60, when the
money runs out in a bad market, why a date) without calling again, and say what an answer assumes when it matters.

Give them the returned url exactly as it is: it opens their quick-start with these numbers filled in, then the
whole plan (stress tests, a year-by-year table, where the money goes). Without `source=agent` the planner opens it
as a shared plan that saves nothing. It runs in their browser with no account, and nothing is saved until they
confirm: the link then becomes a new plan, "From a link", beside any plans they have. The plan keeps the accounts,
spending lines, debts, pension, Social Security and rental income sent. Salary and side income become one monthly
income.

Income is annual. Expenses and contributions are monthly. Amounts in whole currency units (not cents). Growth and
inflation are percentages.

Taxes are off by default, in any country: income is take-home pay. For someone in the US who gives income before
tax, send `taxes=us` (and `state`, a partner, dependents, their Social Security statement figure and a Roth
conversion strategy when they say them): the planner then computes federal, state and payroll tax every year, and
the table gains each year's tax. Amounts are then dollars.

Before retirement, any spending, debt payments and contributions that income doesn't cover are paid from savings.
Without `salary` or `side_income`, and with retirement still ahead, the answer assumes an income that covers
spending, contributions and debt payments until then (`assumed` says so), and the quick-start asks for it.