Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Untilfree - FIRE Calculator

REMOTE · UNTILFREE.MCP.SROFIA.COM

Untilfree FIRE app (App Store, Google Play): your freedom date and FIRE retirement numbers.

+4 this week 77 Trust /100

Last scanned (20 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1508 tokens (~301/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://untilfree.mcp.srofia.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=srofia.com CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 947fa5acbba706d80e1e5f6832682eee
SANs: srofia.com, untilfree.mcp.srofia.com, *.untilfree.mcp.srofia.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of untilfree.mcp.srofia.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
srofia.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://untilfree.mcp.srofia.com/mcp Verified 200
http (plaintext) http://untilfree.mcp.srofia.com/mcp HTTPS enforced 301 https://untilfree.mcp.srofia.com/mcp
MCP tools · 4 exposed · ~1,435 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
calculate_freedom_day ~381

Use this when the user wants a FIRE calculator or asks when can I retire, when can I retire early or stop working, their FIRE number or financial independence date, or how long until work is optional (also retire early in the UK, Canada or Australia), given age, invested savings, monthly investing and monthly spending; or what a purchase or a monthly cost does to that date (how many days of freedom a car, phone, holiday or recurring bill costs, the opportunity cost of buying it). Returns the FIRE number (4% rule by default, adjustable safe withdrawal rate), the date and days left, the age then, a cautious/base/optimistic range and a year-by-year table; with a purchase, also how many days it moves the date and what the money would grow to if invested instead. Ask for any missing number instead of guessing. Do not use for a question about one specific retirement age (use retire_at_age), comparing products or shop prices, loans, stock or fund picks, tax, pension or Social Security benefit rules, or live market data. An estimate, not financial advice.

NameTypeReqDescription
ageintegeryesCurrent age in years.
currencystring–ISO currency code used only for display.
monthlyExpensesnumberyesMonthly spending today; the plan keeps this lifestyle.
monthlyInvestmentnumberyesAmount invested each month.
netWorthnumberyesInvested savings today (not counting the home you live in).
purchaseobject–Optional: a purchase or monthly cost. Adds how many days it moves the freedom day and what the money would grow to if invested instead.
realReturnPctnumber–Yearly growth after inflation, in percent. Default 5.
withdrawalRatePctnumber–Safe withdrawal rate in percent. Default 4.

No output schema declared.

No examples provided.

fire_variants ~414

Use this when the user asks for their coast FIRE number, lean FIRE, fat FIRE or barista FIRE number, a coast FIRE calculator, barista FIRE calculator or FIRE number calculator for a variant, or what the 4% rule gives at leaner or richer spending. Needs age, invested savings, monthly spending and optionally monthly investing and the age to coast to (default 65). Use coast when the user wants to know if they can stop investing and still retire on time (amount needed now to coast to that age). Use barista when the user wants to leave full-time work early and cover the rest with part-time income (part-time income needed on top of what savings pay). Use lean when the user wants the number for a frugal, minimal budget. Use fat when the user wants the number for a comfortable or generous lifestyle. Do not use for an exact retire-at-age check (use retire_at_age), job or salary advice, tax, or picking investments. An estimate, not financial advice.

NameTypeReqDescription
ageintegeryesCurrent age in years.
currencystring–ISO currency code used only for display.
fatMonthlyExpensesnumber–Fat monthly spending. Default 150% of monthlyExpenses.
kindstring–Which FIRE variant: lean, fat, coast, barista, or all.
leanMonthlyExpensesnumber–Lean monthly spending. Default 75% of monthlyExpenses.
monthlyExpensesnumberyesMonthly spending today; the plan keeps this lifestyle.
monthlyInvestmentnumber–Amount invested each month. 0 if nothing.
netWorthnumberyesInvested savings today (not counting the home you live in).
realReturnPctnumber–Yearly growth after inflation, in percent. Default 5.
targetAgeinteger–Traditional retirement age that coast FIRE coasts to. Default 65.
withdrawalRatePctnumber–Safe withdrawal rate in percent. Default 4.

No output schema declared.

No examples provided.

how_long_will_savings_last ~215

Use this when the user asks how long will my savings last at a monthly withdrawal, for example how long will $500k or $1 million last in retirement, how long can I live on $X, will my money last to 90, a career break or sabbatical runway, the 4% rule in reverse, a safe withdrawal rate or whether X% is a safe withdrawal rate. Returns years until it runs out (or that growth covers it), the monthly amount that never runs out, a range and a year-by-year table. Do not use for annuity quotes, pension or Social Security payouts, tax on withdrawals, or choosing investments. An estimate, not financial advice.

NameTypeReqDescription
balancenumberyesSavings today.
currencystring–ISO currency code used only for display.
monthlyWithdrawalnumberyesAmount taken out every month, in today’s money.
realReturnPctnumber–Yearly growth after inflation, in percent. Default 5.

No output schema declared.

No examples provided.

retire_at_age ~425

Use this when the user wants a retirement calculator for a chosen age: "how much do I need to retire", "how much do I need to retire at 45 / 50 / 55 / 60 / 65", "how to retire at 50", "can I retire at 50 with $500k", "am I on track to retire at 55", "when can I retire" at a specific age, or the 25x rule / 4% rule for their spending (also in GBP, CAD, AUD or EUR). Needs monthly or yearly spending in retirement and the target age. Age, invested savings and monthly contribution are optional: without them it returns the amount needed with 4%, 3.5% and 3.3% withdrawal rate variants; with them it adds the age they reach it, the shortfall or surplus at the target age and the extra monthly amount needed. Do not use for an open "when can I retire" question with no age in mind (use calculate_freedom_day), pension, Social Security or annuity amounts and full retirement age rules, tax, or picking investments. An estimate, not financial advice.

NameTypeReqDescription
ageinteger–Current age. Optional; with it the tool shows how far current savings are from the target.
currencystring–ISO currency code used only for display.
monthlyInvestmentnumber–Amount invested each month. Optional, defaults to 0 when age is given.
netWorthnumber–Invested savings today. Optional, defaults to 0 when age is given.
realReturnPctnumber–Yearly growth after inflation, in percent. Default 5.
spendingnumberyesSpending in retirement, in today’s money.
spendingPeriodstring–Whether spending is per month or per year.
targetAgeintegeryesAge at which the person wants to retire or make work optional.
withdrawalRatePctnumber–Safe withdrawal rate in percent. Default 4.

No output schema declared.

No examples provided.

Install

How do I install the Untilfree - FIRE Calculator MCP server?

Untilfree - FIRE Calculator is a hosted endpoint at https://untilfree.mcp.srofia.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · untilfree.mcp.srofia.com

# add to Claude Code
claude mcp add --transport http com-srofia-untilfree 'https://untilfree.mcp.srofia.com/mcp'
Common questions

What is the Untilfree - FIRE Calculator MCP server?

Untilfree - FIRE Calculator is an MCP server listed in the public MCP registry as com.srofia/untilfree. Untilfree FIRE app (App Store, Google Play): your freedom date and FIRE retirement numbers. This page covers its hosted endpoint (https://untilfree.mcp.srofia.com/mcp).

Is the Untilfree - FIRE Calculator MCP server safe to use?

Untilfree - FIRE Calculator scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Untilfree - FIRE Calculator MCP server expose?

Untilfree - FIRE Calculator exposes 4 tools: calculate_freedom_day, how_long_will_savings_last, retire_at_age, fire_variants. Their descriptions and schemas cost roughly 1,435 tokens of context every time the server is loaded.

Does the Untilfree - FIRE Calculator MCP server require authentication?

No. We connected to Untilfree - FIRE Calculator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Untilfree - FIRE Calculator MCP server still maintained?

Untilfree - FIRE Calculator is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Untilfree - FIRE Calculator MCP server?

VerifyMCP ran 14 checks on Untilfree - FIRE Calculator, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.