Remote MCP · Endpoint

Fi-Plan MCP server

No. Fi-Plan answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.fi-plan.in/mcp

The last check completed an MCP handshake.

Registry name
io.github.ompurwar/fi-plan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
891 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Financial simulator for Indian salaries: loans, taxes, SIPs and 50-year FIRE plans.
Listing
From the official MCP registry (active).
Recent checks of Fi-Plan
CheckedResultHandshake
2 hours agoHandshake completed891 ms
2 days agoHandshake completed833 ms
4 days agoHandshake completed840 ms
5 days agoHandshake completed488 ms
7 days agoHandshake completed874 ms
8 days agoHandshake completed974 ms
9 days agoHandshake completed481 ms
12 days agoHandshake completed841 ms
13 days agoHandshake completed481 ms
15 days agoHandshake completed860 ms
17 days agoHandshake completed836 ms
18 days agoHandshake completed481 ms
19 days agoHandshake completed1.20 s
20 days agoHandshake completed848 ms
20 days agoHandshake completed2.08 s
21 days agoHandshake completed846 ms
23 days agoHandshake completed1.89 s

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Fi-Plan and makes no claim about it beyond what these checks measured.