abacus-mcp

# abacus An MCP server that exposes option, portfolio, execution and backtest analytics as tools. ```bash pip install abacus-mcp abacus tools # the whole surface, in one screen abacus stdio # what an MCP client launches ``` > **Not on the package index yet.** The lines above are what they will be. Until > the first release lands, install from source — the server depends on five > sibling libraries, so they go first and then nothing has to be resolved by > name: > > ```bash > pip install \ > "git+https://github.com/DaniyalMlk/moneyness.git" \ > "git+https://github.com/DaniyalMlk/shortfall.git" \ > "git+https://github.com/DaniyalMlk/tenor.git" \ > "git+https://github.com/DaniyalMlk/slippage.git" \ > "git+https://github.com/DaniyalMlk/holdout.git" > pip install "git+https://github.com/DaniyalMlk/abacus.git" > ``` > > `abacus tools` and `abacus stdio` then work exactly as above. Once released, nothing needs installing at all if you have [`uv`](https://docs.astral.sh/uv/) — `uvx abacus-mcp stdio` fetches it, runs it and caches it. Registering it with a client is [one entry naming that command](#registering-it-with-a-client). **[Documentation](https://daniyalmlk.github.io/abacus/)** — the conventions worth reading before the first call, every tool with its arguments, and the numbers this project claims with the test that checks each one. --- Language models are unreliable at arithmetic, so the useful thing a tool boundary can do is move the numbers somewhere trustworthy. `abacus` puts them in libraries whose numerical cores are validated against closed forms, high-precision references and published results, and exposes those cores over the Model Context Protocol. Nothing here wraps a third-party pricing API: the numbers are computed by these libraries and tested where they live. It targets MCP revision **2026-07-28** and has five runtime dependencies, all pure Python: [`moneyness`](https://github.com/DaniyalMlk/moneyness) for the optio…