Fi-Plan
REMOTE · WWW.FI-PLAN.IN · SCANNED SEP 20
Financial simulator for Indian salaries: loans, taxes, SIPs and 50-year FIRE plans.
Available components
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1235 tokens (~308/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 Management30
- Stability observed for 9 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Fi-Plan MCP server?
Fi-Plan is a hosted endpoint at https://www.fi-plan.in/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 · www.fi-plan.in
claude mcp add --transport http ompurwar-fi-plan 'https://www.fi-plan.in/mcp'
{
"mcpServers": {
"ompurwar-fi-plan": {
"url": "https://www.fi-plan.in/mcp"
}
}
} {
"servers": {
"ompurwar-fi-plan": {
"type": "http",
"url": "https://www.fi-plan.in/mcp"
}
}
} [mcp_servers.ompurwar-fi-plan] url = "https://www.fi-plan.in/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ompurwar-fi-plan": {
"type": "remote",
"url": "https://www.fi-plan.in/mcp",
"enabled": true
}
}
} openclaw mcp add ompurwar-fi-plan --url 'https://www.fi-plan.in/mcp' --transport streamable-http
mcp_servers:
ompurwar-fi-plan:
url: "https://www.fi-plan.in/mcp" {
"McpServers": {
"ompurwar-fi-plan": {
"Transport": "http",
"Url": "https://www.fi-plan.in/mcp"
}
}
} assistant mcp add ompurwar-fi-plan -t streamable-http -u 'https://www.fi-plan.in/mcp'
{
"mcpServers": {
"ompurwar-fi-plan": {
"type": "http",
"url": "https://www.fi-plan.in/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 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.
- 13 Sept 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.
- 12 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Sept 26 71
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 20 Sept 2026 · Probed https://www.fi-plan.in/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.fi-plan.in | CN=YR1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 61e9f785bedd239ce4281d25a85bda19fea |
| SANs: www.fi-plan.in | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.fi-plan.in. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| fi-plan.in. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.fi-plan.in/mcp | Verified | 200 | |
| http (plaintext) | http://www.fi-plan.in/mcp | HTTPS enforced | 308 | https://www.fi-plan.in/mcp |
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 →
asset_projection Project a single asset month-by-month ~378
Pure calculator for one asset (no plan needed): monthly value, invested, growth, income and TDS over duration months. Pass asset parameters (principal, growth_rate, yield_rate, income_frequency, income_mode, maturity_month, sale_month, sip) — class presets are NOT applied automatically, so pass explicit rates. TDS on FD interest follows the stored rules for the assessment_year. Returns rows plus closing value and totals.
| Name | Type | Req | Description |
|---|---|---|---|
| assessment_year | string | – | Assessment year for tax rules, e.g. '2025-26' (default: current). |
| asset_class | string | – | Asset type; affects default tax treatment (default 'fd'). |
| category | string | – | Bucket: s = savings, e = expenses, i = investments (default 'i'). |
| compounding | string | – | Compounding mode for growth (default none). |
| duration | integer | – | Projection length in months (default 120). |
| growth_rate | number | yes | Annual capital growth rate in percent. |
| income_frequency | string | – | Income payout frequency: m monthly, q quarterly, h half-yearly, y yearly. |
| income_mode | string | – | Where income goes: credit (cash) or reinvest. |
| maturity_month | integer | – | Month the asset matures; value is released then. |
| principal | number | yes | Starting value/principal in rupees. |
| purchase_month | integer | – | Month the asset is acquired (default 1). |
| rent | object | – | Real-estate rent settings. |
| sale_month | integer | – | Month the asset is sold. |
| sip | object | – | Optional recurring SIP into the asset. |
| title | string | – | Display name for the asset (defaults to 'Asset'). |
| yield_rate | number | – | Annual income/yield rate in percent (interest, dividend, rent). |
No output schema declared.
No examples provided.
loan_amortization Compute a loan amortization schedule ~269
Pure calculation of EMI and a month-by-month amortization schedule for a loan of amount at annual interest_rate over tenure months. Returns opening/closing balance, interest, principal and running totals per month. Pass optional prepayments to model extra principal payments beyond the EMI (each {start_month, amount, frequency: 'm'|'q'|'y'|null, step_pct?} — null frequency = one-time lump, step_pct = % the amount grows by each recurrence): the EMI stays constant, the loan shortens, and the result becomes { schedule, payoff_month, total_interest_paid, total_prepaid, interest_saved } instead of a plain array. NOTE: here start_month is loan-relative (1 = the loan's first EMI month); on a persisted loan the same fields are plan-absolute months.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Loan principal in rupees (e.g. 1500000 for ₹15,00,000). |
| interest_rate | number | yes | Annual interest rate in percent (e.g. 8.6). |
| prepayments | array | – | Optional extra principal payments beyond the EMI: the EMI stays constant and the loan shortens. |
| tenure | number | yes | Loan tenure in months (e.g. 240 for 20 years). |
No output schema declared.
No examples provided.
loan_refinance Analyze refinancing a loan at a new rate ~224
Pure what-if: closes the loan at refinance_month (outstanding balance settled) and restarts it at new_rate over new_tenure months. Returns outstanding balance, old vs new EMI, remaining interest vs new total interest, interest_saved, net_savings (after optional foreclosure_charge) and breakeven_months (null when the new EMI is not lower). Read-only — to persist, update the old loan's end_month and add the new loan.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Outstanding loan principal at refinance_month, in rupees. |
| foreclosure_charge | number | – | Foreclosure/prepayment penalty in rupees (default 0). |
| interest_rate | number | yes | Current annual interest rate in percent. |
| new_rate | number | yes | Annual interest rate of the new loan in percent. |
| new_tenure | integer | yes | Tenure of the new loan in months. |
| refinance_month | integer | yes | Loan-relative month the refinance happens (outstanding balance is settled). |
| tenure | integer | yes | Total tenure of the existing loan in months. |
No output schema declared.
No examples provided.
simulate_plan Run a what-if scenario on a plan ~364
Applies an ordered list of scenario patches to a DEEP COPY of the plan (never persisted) and returns the resulting snapshot plus applied_patches. Pass plan_id to load the plan server-side (preferred — never paste plan_json); plan_json is accepted for portability. Pass summary=true for the compact view; add milestones=true for long durations to get yearly points + totals instead of every month. Patches support add_income, add_expense, add_cashflow_change, add_loan, update_loan (loan_id plus any of title, principal_amount, interest_rate, start_month, end_month, deposit_to_bank, type, ref_id, prepayments), add_fdp (fdp: { start_month, end_month, s, e, i } with s + e + i = 100 — or the legacy { amount, interest_rate, tenure } fixed-deposit shape) and set_account_balance — nested ({"op":"add_cashflow_change","change":{...}}) and flat ({cashflow_id,value,start_month,...}) forms are both accepted; the op is inferred from the fields.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | number | – | Projection length in months (public tier caps this). |
| milestones | boolean | – | With summary, return yearly points and totals instead of every month. |
| patches | array | – | Ordered scenario patches (add_income, add_expense, add_cashflow_change, add_loan, update_loan, add_fdp, set_account_balance). |
| plan_id | string | – | Load a saved plan by id (authenticated tier only). |
| plan_json | object | – | Inline plan object for anonymous use; bounded to 256 KB. |
| summary | boolean | – | Return the compact summary (monthly totals + balances) instead of the full snapshot. |
No output schema declared.
No examples provided.
What is the Fi-Plan MCP server?
Fi-Plan is an MCP server listed in the public MCP registry as io.github.ompurwar/fi-plan. Financial simulator for Indian salaries: loans, taxes, SIPs and 50-year FIRE plans. This page covers its hosted endpoint (https://www.fi-plan.in/mcp).
Is the Fi-Plan MCP server safe to use?
Fi-Plan scores 75 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 Fi-Plan MCP server expose?
Fi-Plan exposes 4 tools: simulate_plan, loan_amortization, loan_refinance, asset_projection. Their descriptions and schemas cost roughly 1,235 tokens of context every time the server is loaded.
Does the Fi-Plan MCP server require authentication?
No. We connected to Fi-Plan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fi-Plan MCP server still maintained?
Fi-Plan is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.