firenum retirement planner MCP server
com.firenum/fire-plannerfirenum.comstreamable-httpv1.4.2Scanned
When can you retire? A FIRE plan from your numbers, graded by Monte Carlo and every year since 1872.
1 tool: 1 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the firenum retirement planner MCP server can do
The firenum retirement planner MCP server is published by firenum.com, a domain the MCP Registry verified. It has 1 tool. It can create or change data (1 tool: build_retirement_plan), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.4.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Changes things 1Claude Code: ask
build_retirement_planUse 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 gav…1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 3,791 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...d debt payments until then (`assumed` says so), and the quick-start asks for it."
Description, as the server wrote it 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 plan, the whole planner (stress tests, a year-by-year table, where the money goes), as a new plan, "From a link", beside any plans they have. A link without an age, spending or income opens the quick-start with these numbers filled in instead, and asks for the rest. Without `source=agent` the planner opens it as a shared plan that saves nothing. It runs in their browser with no account. 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.
Annotations the server declares
- title: Build a retirement plan
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://firenum.com/mcp: tools/list returned 1 tool to an anonymous client, including build_retirement_plan (write)
Findings
Matches of fixed checks, with the text they matched.
The description is 3,791 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...d debt payments until then (`assumed` says so), and the quick-start asks for it."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:build_retirement_planChanges thingsdescriptioninputSchema
Tools1 changed.~1 changedView diff
- Changed:build_retirement_planChanges thingsinputSchema
Tools1 changed.~1 changedView diff
- Changed:build_retirement_planChanges thingsinputSchema
Install
Pinned to version 1.4.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http fire-planner https://firenum.com/mcpclaude mcp add --transport http fire-planner https://firenum.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__fire-planner__build_retirement_plan"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fire-planner. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.firenum/fire-planner/verify?hash=f16586709240086d78d6b7ea0e7e6c8b08e68c4549043cc06d2bfca631f551cc" | jq -e '.changed == false'Pinned hash f16586709240, from Nov 9, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.firenum/fire-planner/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.firenum/fire-planner)Source: MCP Registry. Synced Oct 24, 2026, 21:17 UTC.
firenum retirement planner MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the firenum retirement planner MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the firenum retirement planner MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the firenum retirement planner MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the firenum retirement planner MCP server have?
- 1 tool: 1 write. build_retirement_plan.
Does the firenum retirement planner MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the firenum retirement planner MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the firenum retirement planner MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.