Best used with an AI agent

40+ live apps, open data APIs, MCP servers, and 200+ guides - more than anyone wants to click through. Point your AI here and it reads the whole map and does the work: finds the tool, pulls the data, runs the analysis, and hands you the links.

Here for the open-source code? Your agent finds the right repo for you - and can even clone and deploy it.

Prefer to explore on your own? Go right ahead.

Paste this to Claude Code, Codex, or any AI agent:
Go to tigzig.com and read tigzig.com/llms.txt. It is a practitioner toolkit - 40+ analytics apps, open no-auth data APIs, MCP servers, open-source repos (github.com/amararun), and 200+ build guides. Help me [your task]. Surface the exact links; where there is an API or MCP, call it directly; and if I want to self-host, find the repo and help me deploy it.

Standard Deviation (Volatility)

How spread out a fund’s returns are around the average.

Source data: AMFI daily NAV (17,900+ schemes) + Nifty benchmark indices · Last updated: 2026-07-02 · Open the MFPRO tool

What is Standard Deviation?

Standard deviation measures how spread out the rolling returns are around the average. Higher std dev = more volatile = wider range of outcomes. A fund with 12% avg return and 8% std dev is more predictable than one with 12% avg and 20% std dev.

How We Compute It

StdDev = √(Σ(ri − avg)2 / (n − 1))

We use sample standard deviation (divide by n−1), which matches DuckDB's STDDEV function. With hundreds or thousands of observations, the difference between sample and population std dev is negligible.

This is computed over the rolling return observations, not daily NAV changes.

How to Interpret

Two funds with same average return

Fund A: Avg 15%, StdDev 6% → Returns typically range 9% to 21%

Fund B: Avg 15%, StdDev 14% → Returns typically range 1% to 29%

Same average, but Fund B has a much wider range of outcomes. The "typical range" is roughly avg ± 1 std dev.

Related metrics

More Returns methodology from the MFPRO analytics tool: