# Fi-Plan (remote · www.fi-plan.in)

Financial simulator for Indian salaries: loans, taxes, SIPs and 50-year FIRE plans.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `www.fi-plan.in`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ompurwar-fi-plan/www.md), [page](https://verifymcp.io/servers/ompurwar-fi-plan/www)

## Channel facts

- Endpoint: `https://www.fi-plan.in/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ompurwar-fi-plan 'https://www.fi-plan.in/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ompurwar-fi-plan": {
      "url": "https://www.fi-plan.in/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ompurwar-fi-plan": {
      "type": "http",
      "url": "https://www.fi-plan.in/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ompurwar-fi-plan]
url = "https://www.fi-plan.in/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ompurwar-fi-plan": {
      "type": "remote",
      "url": "https://www.fi-plan.in/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ompurwar-fi-plan --url 'https://www.fi-plan.in/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ompurwar-fi-plan:
    url: "https://www.fi-plan.in/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ompurwar-fi-plan": {
      "Transport": "http",
      "Url": "https://www.fi-plan.in/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ompurwar-fi-plan -t streamable-http -u 'https://www.fi-plan.in/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 75, +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.

### 2026-09-18 (score 74, +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.

### 2026-09-16 (score 73, +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.

### 2026-09-13 (score 72, +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.

### 2026-09-12 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-11 (score 71)

First indexed and scored.

## MCP tools (4)

### `simulate_plan` (~364 tokens)

Run a what-if scenario on a plan

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.

Input parameters:

- `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.

### `loan_amortization` (~269 tokens)

Compute a loan amortization schedule

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.

Input parameters:

- `amount` (number, required): Loan principal in rupees (e.g. 1500000 for ₹15,00,000).
- `interest_rate` (number, required): 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, required): Loan tenure in months (e.g. 240 for 20 years).

### `loan_refinance` (~224 tokens)

Analyze refinancing a loan at a new rate

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.

Input parameters:

- `amount` (number, required): Outstanding loan principal at refinance_month, in rupees.
- `foreclosure_charge` (number): Foreclosure/prepayment penalty in rupees (default 0).
- `interest_rate` (number, required): Current annual interest rate in percent.
- `new_rate` (number, required): Annual interest rate of the new loan in percent.
- `new_tenure` (integer, required): Tenure of the new loan in months.
- `refinance_month` (integer, required): Loan-relative month the refinance happens (outstanding balance is settled).
- `tenure` (integer, required): Total tenure of the existing loan in months.

### `asset_projection` (~378 tokens)

Project a single asset month-by-month

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.

Input parameters:

- `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, required): 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, required): 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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ompurwar-fi-plan/www#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 71
- 2026-09-11: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://www.fi-plan.in/mcp
- Repository: https://github.com/ompurwar/fi-plan-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ompurwar-fi-plan/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/ompurwar-fi-plan/www.json
- HTML version of this page: https://verifymcp.io/servers/ompurwar-fi-plan/www