mcpbeat Sign in

firenum retirement planner MCP Server

answering

firenum retirement planner is answering right now. Last checked 8 min ago. It exposes 1 tools.

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

Uptime history 21 days of history · worst day 99%
21 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
258 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 October 2026. No other catalogue keeps this.

24 Oct a tool changed the parameters it asks for2 times that day build_retirement_plan
24 Oct a tool changed version2 times that day
19 Oct a tool description was rewritten build_retirement_plan
19 Oct a tool changed the parameters it asks for build_retirement_plan
19 Oct a tool changed version
and 2 more, back to 19 October 2026

firenum retirement planner missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add fire-planner --transport http https://firenum.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://firenum.com/mcp
~/.codex/config.toml
[mcp_servers.fire-planner]
url = "https://firenum.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fire-planner": {
      "url": "https://firenum.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "fire-planner": {
      "type": "http",
      "url": "https://firenum.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

build
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.

Endpoints

URLTransportStateLatencyChecked
https://firenum.com/mcp streamable-http answering 221 ms 8 min ago

Alternatives to firenum retirement planner

same job, measured the same way
Planomy Planner
by demorphed6-lgtm

Retirement planning on your own machine: projections, Monte Carlo, scenarios, budgets, plan edits.

local only
BotPhone
by botphone

Give any AI agent a phone number. BotPhone answers your business line and reports every call back.

answering
Botphone
by griffden

Give your Muse a phone number. BotPhone answers your business line and reports every call back.

answering
NumRadar
by numradar

Check whether phone numbers are registered on WhatsApp, from your AI agent.

203 installs/wk answering
Glacier Planner: Free Canadian Retirement Calculator
by marcpineault

Free Canadian retirement projections and one what-if from confirmed inputs. No Glacier account.

1 tools answering
SecScan
by secscan

Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.

12 tools answering
Greener Ahead
by greenerahead

Your carbon footprint, VSME and CSRD reports and climate plan, with the source of every figure.

answering
Asset Management
by disin7c9

Drawdown-first risk for your stock/ETF book — every number from a validated core, not the model.

local only

firenum retirement planner — questions

Answers built from our own checks of this server.

What can firenum retirement planner do?
It exposes 1 tools, read directly from the server on our last check. Among them: build_retirement_plan. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is firenum retirement planner working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 258 ms. The bar chart above shows every period we have measured.
How do I connect firenum retirement planner?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does firenum retirement planner need an API key?
No. firenum retirement planner completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is firenum retirement planner?
It answers our handshake in 258 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.