pyvar-mcp
MCP server exposing all 385 pyvar.com risk functions — VaR, credit risk, derivatives, liquidity, operational risk, portfolio analytics, ALM, regulatory capital — as Claude Code tools.
It's a thin wrapper over the live pyvar API (each tool call is a real HTTPS request), not a bundled copy of the compute engine — results always match what's actually deployed at pyvar.com.
Install
/plugin marketplace add fibtecltd/pyvar
/plugin install pyvar-mcp@pyvar-marketplace
You'll be prompted for a pyvar API key during install. Sign in at
https://www.pyvar.com#get-api-key (emailed link or Google; no password, no
credit card) and create one on the dashboard. It starts with pyvar_, lasts a
year, and you can revoke it there at any time.
The plugin starts the server with uvx pyvar-mcp, which downloads it from PyPI
on first use, so it needs uv on your PATH. If the
tool calls fail with a "command not found" style error, a missing uv is almost
certainly why. No uv? Run pip install pyvar-mcp and change the plugin's
mcpServers command to pyvar-mcp (with no args). Working from a checkout of
this repo instead: pip install -e plugins/mcp.
pyvar-mcp is published to PyPI by .github/workflows/pyvar-mcp-publish.yml
when a pyvar-mcp-v* tag is pushed (trusted publishing; the tag must equal the
version in pyproject.toml).
Tools
Two generic tools, meant as your first choice:
list_pyvar_functions(domain?)— browse available functions, optionally filtered to one domain (alm,credit-risk,derivatives,liquidity,market-risk,operational,portfolio,regulatory).call_pyvar_function(domain, function_name, params)— call any function by name. Validatesparamsagainst the function's own schema before calling the API.
Plus all 385 functions as individually named tools (alm_stress_test,
historical_simulation_var, etc.) with precise per-parameter schemas, for
when you already know exactly which one you want.
Local development
cd plugins/mcp
pip install -e ".[dev]"
pytest
Regenerating the tool catalogue after portal/functions.json changes:
python3 scripts/generate_mcp_tools.py # from the repo root
.github/workflows/plugins-ci.yml fails CI if the committed
pyvar_mcp/_generated/functions.py doesn't match what regenerating produces
— same drift-check pattern the skills plugins and pyvar-client use.
Metadata
Release files for pyvar-mcp 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyvar_mcp-0.2.1.tar.gz | 94.5 kB | With provenance | Details for pyvar_mcp-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyvar_mcp-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for pyvar_mcp-0.2.1-py3-none-any.whl |
Total release size: 186.4 kB
Release files / pyvar_mcp-0.2.1.tar.gz
| Download URL | pyvar_mcp-0.2.1.tar.gz |
|---|---|
| Size | 94.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33e888f6a34b3cadaff7d34c943468e67b5d67f38e68a8056023d9e53892e2d8
|
|
BLAKE2b-256 checksum How to use checksums |
212685810f0296b936ba723e04656d59ccacd838e5f7d87ad23caf4fd4c8c6ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / pyvar_mcp-0.2.1-py3-none-any.whl
| Download URL | pyvar_mcp-0.2.1-py3-none-any.whl |
|---|---|
| Size | 91.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a6654c60d66f002019be2c0bdb1b2e052503f68f42b465156008aef7716d86d9
|
|
BLAKE2b-256 checksum How to use checksums |
d088784d710f1e88c08f8aca6417cbe531fd775d58b9e2c8858a459ce7fbe337
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logSecurity for pyvar-mcp 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyvar_mcp-0.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.