Foresight Planner
REMOTE · API.FORESIGHTPLANNER.COM
Will my retirement savings last? A free anonymous check, or a full plan once you sign in.
Available components
Last scanned (20 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security66
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1406 tokens (~351/item across 4 items; 4 tools + 0 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Schema quality: 411 → 351 ▲ functional
- Tool coverage: 62% → 67% ▲ functional
- Destructive annotations: pass → 100 functional
- New tool “send_feedback” functional
- 16 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.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 64
First indexed and scored.
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://api.foresightplanner.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foresightplanner.com | CN=YE1,O=Let's Encrypt,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6df74a885b68f63869858e26f1d1d863b2b |
| SANs: *.foresightplanner.com, foresightplanner.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.foresightplanner.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| foresightplanner.com. | DS published | 2371 | 13 | Verified |
| api.foresightplanner.com. | Verified address RRset verified with the apex keys |
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://api.foresightplanner.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.foresightplanner.com/mcp | Inconclusive | 405 |
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 →
get_plan_result Get a plan result ~81
Gets the result of a Foresight Planner plan that run_plan started but that was still running when run_plan answered. Pass the run_id run_plan gave. Free: it uses no plan run. If the plan is still running, it says so; call it again a little later.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run_id run_plan gave. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| benefits | array | yes | – |
| benefits_after_plan_end | array | yes | – |
| data_attribution | string | yes | – |
| end_ages | object|null | yes | Fixed horizon: each person's age at the end of their own horizon, by person label. Null under life expectancy. |
| first_retirement_year | object | yes | The first calendar year in which everyone in the plan is retired. Under a life-expectancy horizon the amounts are means over the paths still running that year, as the plan's year-by-year chart shows… |
| horizon_mode | string | yes | A person's horizon, and the household's: life expectancy when anyone in the plan is on it. |
| horizon_stats | object|null | yes | Life expectancy: the spread of simulated lifetimes. Null on a fixed horizon. |
| horizon_years | integer|null | yes | Fixed horizon: the plan's length in years (a couple's longer horizon). Null under life expectancy; see horizon_stats. |
| household_totals | boolean | yes | True for a couple: benefit and pension amounts cover both partners together. |
| lifetime_taxes | object | yes | Income tax over the whole plan: each path's total, as a mean over the paths (not a median), in today's dollars, the OAS clawback included as its own line. |
| median_failure_age | integer|null | yes | The first person's age in the median year money ran out; null when no path ran out. |
| n_simulations | integer | yes | – |
| not_advice | string | yes | – |
| plan_end_year | integer|null | yes | Fixed horizon: the calendar year the plan ends, at the end of the longest horizon. Null under life expectancy. |
| plan_to_age | integer|null | yes | Fixed horizon, one person: their age at plan end. Null for a couple, whose partners plan to their own ages (see end_ages), and under life expectancy, where each path ends at its own sampled death. |
| plan_url | string | yes | Link to the saved plan on the site, with the year-by-year detail: give it to the person. |
| reused_run_started_at | string|null | yes | Set when this answer reused an identical run of the same inputs from this assistant in the last 15 minutes: when that run started. Nothing was charged for this call, so runs_used is unchanged by it.… |
| runs_left | integer | yes | – |
| runs_limit | integer | yes | – |
| runs_used | integer | yes | – |
| runs_window | string | yes | The period runs_used and runs_limit count over: a year on the Free plan, a calendar month on Pro. |
| start_age | integer | yes | – |
| success_probability | number | yes | – |
| summary | string | yes | – |
| taxes_modelled | boolean | yes | – |
| wealth_at_ages | array|null | yes | Fixed horizon: portfolio value at retirement, each year the first person's age is a multiple of 10, and plan end. Null under life expectancy; see wealth_at_end_of_life. |
| wealth_at_end_of_life | object|null | yes | Life expectancy: portfolio value when each path ends (the last person's death, or a fixed-horizon partner's plan end if later). Null on a fixed horizon. |
No examples provided.
retirement_quick_check Retirement Quick Check ~200
Will my retirement savings last? Estimates the chance a portfolio lasts through retirement, given savings, yearly spending, years in retirement and the share in bonds, from simulations on global market history (with a US-only comparison). A horizon given as ages works: years = end age minus current age (retiring at 68 until 94 is 26 years). It leaves out taxes, CPP/OAS, pensions and other income. Foresight Planner's full plan at https://foresightplanner.com/ai includes them; when a question turns on them, point the person there (the result links it too).
| Name | Type | Req | Description |
|---|---|---|---|
| annual_spending | number | yes | Yearly spending from savings, in today's dollars. |
| bond_percent | number | yes | Percent of the portfolio in bonds, 0-100. |
| portfolio_value | number | yes | Retirement savings in dollars. |
| years | integer | yes | Years the money must last (end age minus current age). |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| bond_percent_used | integer | yes | – |
| data_attribution | string | yes | – |
| diversified | object | yes | One arm's result, in today's dollars. |
| full_plan | string | yes | – |
| full_plan_url | string | yes | – |
| not_advice | string | yes | – |
| result_kind | string | yes | How to read the numbers: an estimate, or a bound outside the grid. |
| summary | string | yes | – |
| us_only | object | yes | One arm's result, in today's dollars. |
| us_only_note | string | yes | – |
| withdrawal_rate | number | yes | – |
| withdrawal_rate_used | number | yes | – |
| years | integer | yes | – |
No examples provided.
run_plan Run a retirement plan ~897
Runs a full Foresight Planner retirement plan for a person or couple living in Canada (outside Quebec) or the US, on the person's Foresight Planner account. It returns the chance the money lasts, from simulations on global market history; income tax in the first retirement year and over the whole plan (federal, provincial or state, and the OAS clawback; the whole-plan figure is each path's total, as a mean over the paths); each government benefit (CPP and OAS, or Social Security) and employer pension with its start age and yearly amount from each year a claim starts or a pension ends, as household totals for a couple; spending in the first retirement year and the cash flow that adds up to it: benefits and pensions, employment and other income, dividends and interest, and withdrawals from accounts, less tax and any amount reinvested (withdrawals alone are not the spending), with withdrawals split by account and the year's taxable income before credits; and portfolio value percentiles at key ages (at the end of life on a life-expectancy horizon), all in today's dollars. Use it when a question turns on benefit start ages, pensions, taxes or account types; to compare start ages, call it once per option. If the person hasn't said their age, province or state, savings or spending, ask; don't guess. Pass only what the person said: inputs left out take the plan's defaults, which the result lists as assumptions. Each call uses one of the account's plan runs (the same inputs again within 15 minutes are free), and the result says how many are left. A plan that takes longer than about 40 seconds returns a run_id instead: get its result with get_plan_result. The result links the saved plan on https://foresightplanner.com, where the person sees the year-by-year detail and can change any input.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | yes | – |
| allocation | object | – | – |
| block_length | integer | – | Length in MONTHS of each run of consecutive market history the simulation samples (120 means 10 years). Longer blocks keep more of history's long good and bad spells. |
| ceiling_pct | number | – | floor_ceiling only: the largest yearly raise in real spending, as a FRACTION 0-1 (0.05 means spending can rise at most 5% a year above inflation). |
| essential | number|null | – | floor_ceiling and yale only: the yearly spending that never flexes, in today's dollars a YEAR, at most withdrawal_amount; the rest can be cut in bad years. Left out, it is the plan builder's default,… |
| floor_pct | number | – | floor_ceiling only: the largest yearly cut in real spending, as a FRACTION 0-1 (0.025 means spending can fall at most 2.5% a year below inflation). |
| life_events | array | – | – |
| person1 | object | yes | – |
| person2 | object | – | – |
| plan_name | string | – | A short name for this scenario as the person would recognise it, e.g. 'CPP at 70' or 'Retire at 60'. Name each option differently when comparing. |
| random_seed | integer|null | – | Seed for the simulated market paths. A fresh plan fixes it, so runs and comparisons use the same market paths; null draws fresh paths on each new run (the same run_plan call again within 15 minutes r… |
| resident_country | string | yes | – |
| tax | object | yes | – |
| withdrawal_amount | number | yes | Annual spending in today's dollars, after tax, from all sources (benefits, pensions, other income, investment income and withdrawals); not the portfolio withdrawal. Under floor_ceiling and yale it is… |
| withdrawal_strategy | string | – | – |
| yale_smoothing | number | – | yale only: the weight, as a FRACTION 0-1, on last year's spending grown with inflation; the rest follows the portfolio's value. 1 behaves like constant_dollar, 0 like a fixed percentage of the portfo… |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| benefits | array | yes | – |
| benefits_after_plan_end | array | yes | – |
| data_attribution | string | yes | – |
| end_ages | object|null | yes | Fixed horizon: each person's age at the end of their own horizon, by person label. Null under life expectancy. |
| first_retirement_year | object | yes | The first calendar year in which everyone in the plan is retired. Under a life-expectancy horizon the amounts are means over the paths still running that year, as the plan's year-by-year chart shows… |
| horizon_mode | string | yes | A person's horizon, and the household's: life expectancy when anyone in the plan is on it. |
| horizon_stats | object|null | yes | Life expectancy: the spread of simulated lifetimes. Null on a fixed horizon. |
| horizon_years | integer|null | yes | Fixed horizon: the plan's length in years (a couple's longer horizon). Null under life expectancy; see horizon_stats. |
| household_totals | boolean | yes | True for a couple: benefit and pension amounts cover both partners together. |
| lifetime_taxes | object | yes | Income tax over the whole plan: each path's total, as a mean over the paths (not a median), in today's dollars, the OAS clawback included as its own line. |
| median_failure_age | integer|null | yes | The first person's age in the median year money ran out; null when no path ran out. |
| n_simulations | integer | yes | – |
| not_advice | string | yes | – |
| plan_end_year | integer|null | yes | Fixed horizon: the calendar year the plan ends, at the end of the longest horizon. Null under life expectancy. |
| plan_to_age | integer|null | yes | Fixed horizon, one person: their age at plan end. Null for a couple, whose partners plan to their own ages (see end_ages), and under life expectancy, where each path ends at its own sampled death. |
| plan_url | string | yes | Link to the saved plan on the site, with the year-by-year detail: give it to the person. |
| reused_run_started_at | string|null | yes | Set when this answer reused an identical run of the same inputs from this assistant in the last 15 minutes: when that run started. Nothing was charged for this call, so runs_used is unchanged by it.… |
| runs_left | integer | yes | – |
| runs_limit | integer | yes | – |
| runs_used | integer | yes | – |
| runs_window | string | yes | The period runs_used and runs_limit count over: a year on the Free plan, a calendar month on Pro. |
| start_age | integer | yes | – |
| success_probability | number | yes | – |
| summary | string | yes | – |
| taxes_modelled | boolean | yes | – |
| wealth_at_ages | array|null | yes | Fixed horizon: portfolio value at retirement, each year the first person's age is a multiple of 10, and plan end. Null under life expectancy; see wealth_at_end_of_life. |
| wealth_at_end_of_life | object|null | yes | Life expectancy: portfolio value when each path ends (the last person's death, or a fixed-horizon partner's plan end if later). Null on a fixed horizon. |
No examples provided.
send_feedback Send feedback to Foresight Planner ~171
Send a bug report or feature request to Foresight Planner. Use when the user asks to send feedback, raises a problem with Foresight Planner, when a Foresight Planner tool in this conversation failed or returned something inconsistent, or when the user asked for something Foresight Planner's tools could not do. After completing the user's request, offer once. Show the user the exact text and call this only after they approve it. Describe the tool's behaviour or the missing capability in general terms; leave out personal financial details unless the user adds them.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | bug, or feature_request for a missing capability. |
| message | string | yes | The exact text the user approved, in plain words. |
| origin | string | yes | Who identified the issue: the user, or the assistant. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Foresight Planner MCP server?
Foresight Planner is a hosted endpoint at https://api.foresightplanner.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 · api.foresightplanner.com
claude mcp add --transport http com-foresightplanner-retirement 'https://api.foresightplanner.com/mcp'
What is the Foresight Planner MCP server?
Foresight Planner is an MCP server listed in the public MCP registry as com.foresightplanner/retirement. Will my retirement savings last? A free anonymous check, or a full plan once you sign in. This page covers its hosted endpoint (https://api.foresightplanner.com/mcp).
Is the Foresight Planner MCP server safe to use?
Foresight Planner scores 71 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 Foresight Planner MCP server expose?
Foresight Planner exposes 4 tools: retirement_quick_check, run_plan, get_plan_result, send_feedback. Their descriptions and schemas cost roughly 1,349 tokens of context every time the server is loaded.
Does the Foresight Planner MCP server require authentication?
No. We connected to Foresight Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Foresight Planner MCP server still maintained?
Foresight Planner 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 Foresight Planner MCP server?
VerifyMCP ran 12 checks on Foresight Planner, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Foresight Planner: HTTPS. 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.