firenum retirement planner

com.firenumPublished by firenum.comOfficial publisherv1.4.2Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

A remote retirement-planning server that turns a person's age, income, savings, spending and debts into a FIRE plan with a shareable plan link.

What you can do
Build a retirement plan from supplied numbers: age, income, savings, spending and debts, plus the FIRE variant asked about (Coast, Barista, Lean or Fat). Answer questions such as when someone can retire, whether their money will last, and their FIRE number. Return the answer together with a link to the generated plan. The plan is graded by Monte Carlo simulation and against historical years since 1872.
When to use it
Useful when someone wants a quick, quantified retirement or FIRE projection and is willing to share their financial figures with the assistant. Suited to personal planning conversations rather than detailed portfolio or tax advice.
Requirements
A remote streamable HTTP endpoint at firenum.com; no package, account, API key or header is declared. The assistant needs the user's age, income, savings, spending and debts to build a plan.
Before you install
The user's financial figures (age, income, savings, spending, debts) are sent to a third-party service, and the result includes a plan link that may expose those figures to anyone holding it. Projections are simulations, not guarantees; no authentication is declared, so consider what is shared.

Installation

In SourceWeft

  1. Open firenum retirement planner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.firenum%2Ffire-planner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

1

build_retirement_plan

Build a 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 with

Parametershsapiacashdebtfoodrothbirthstatetaxescryptogrowthretire+40 more

Version history

4
  1. v1.4.2LatestOct 25, 2026
  2. v1.4.1Oct 24, 2026
  3. v1.4.0Oct 19, 2026
  4. v1.3.0Oct 13, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.