pyvar-mcp 0.2.0__tar.gz

pyvar_mcp-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing
+      the origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Fibtec Limited
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

pyvar_mcp-0.2.0/PKG-INFO

@@ -0,0 +1,100 @@
+Metadata-Version: 2.4
+Name: pyvar-mcp
+Version: 0.2.0
+Summary: MCP server exposing pyvar.com's 385 risk functions as Claude Code tools
+Author: Fibtec Limited
+License: Apache-2.0
+Project-URL: Homepage, https://www.pyvar.com
+Project-URL: Repository, https://github.com/fibtecltd/pyvar
+Project-URL: Bug Tracker, https://github.com/fibtecltd/pyvar/issues
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Office/Business :: Financial
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: mcp<3,>=2.1.0
+Requires-Dist: anyio>=4.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.24; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: black==26.5.1; extra == "dev"
+Requires-Dist: isort==8.0.1; extra == "dev"
+Requires-Dist: ruff==0.15.22; extra == "dev"
+Dynamic: license-file
+
+# pyvar-mcp
+
+MCP server exposing all 385 [pyvar.com](https://www.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](https://docs.astral.sh/uv/) on your PATH. 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; until the first release exists, use the
+checkout install above.
+
+This installs the `pyvar-mcp` console command the plugin's `mcpServers`
+config invokes. If the tool calls fail with a "command not found" style
+error, this step is almost certainly why. A future revision may publish
+`pyvar-mcp` to PyPI (mirroring `pyvar-client`'s own release workflow) and
+switch the plugin to `uvx pyvar-mcp`, removing this step entirely — tracked
+as an open question in `docs/p10-skills-and-plugin-plan.md`.
+
+## 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. Validates `params` against 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.

pyvar_mcp-0.2.0/README.md

@@ -0,0 +1,71 @@
+# pyvar-mcp
+
+MCP server exposing all 385 [pyvar.com](https://www.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](https://docs.astral.sh/uv/) on your PATH. 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; until the first release exists, use the
+checkout install above.
+
+This installs the `pyvar-mcp` console command the plugin's `mcpServers`
+config invokes. If the tool calls fail with a "command not found" style
+error, this step is almost certainly why. A future revision may publish
+`pyvar-mcp` to PyPI (mirroring `pyvar-client`'s own release workflow) and
+switch the plugin to `uvx pyvar-mcp`, removing this step entirely — tracked
+as an open question in `docs/p10-skills-and-plugin-plan.md`.
+
+## 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. Validates `params` against 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.

pyvar_mcp-0.2.0/pyproject.toml

@@ -0,0 +1,68 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "pyvar-mcp"
+version = "0.2.0"
+description = "MCP server exposing pyvar.com's 385 risk functions as Claude Code tools"
+readme = "README.md"
+license = { text = "Apache-2.0" }
+authors = [{ name = "Fibtec Limited" }]
+requires-python = ">=3.11"
+# mcp is the one real runtime dependency -- the actual pyvar API calls use
+# stdlib urllib (see pyvar_mcp/client.py's own docstring for why), not a
+# second HTTP stack; mcp itself pulls in httpx transitively but only for
+# the MCP protocol wire format, unrelated to this server's own API calls.
+dependencies = ["mcp>=2.1.0,<3", "anyio>=4.0"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Financial and Insurance Industry",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Office/Business :: Financial",
+]
+
+[project.urls]
+Homepage = "https://www.pyvar.com"
+Repository = "https://github.com/fibtecltd/pyvar"
+"Bug Tracker" = "https://github.com/fibtecltd/pyvar/issues"
+
+[project.scripts]
+pyvar-mcp = "pyvar_mcp.main:main"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8.0",
+    "pytest-asyncio>=0.24",
+    "pytest-cov",
+    "black==26.5.1",
+    "isort==8.0.1",
+    "ruff==0.15.22",
+]
+
+[tool.setuptools.packages.find]
+include = ["pyvar_mcp*"]
+
+[tool.black]
+line-length = 100
+
+[tool.isort]
+profile = "black"
+line_length = 100
+known_first_party = ["pyvar_mcp"]
+# Explicit, not a guess: isort's local-package auto-detection, run from this
+# directory, misclassifies the third-party `mcp` PyPI package (mcp.types,
+# mcp.server.*) as first-party -- this project's own directory is named
+# plugins/mcp/, and isort's heuristic conflates the project root's basename
+# with the module name "mcp" it's trying to classify. Confirmed directly via
+# `isort.place_module("mcp", config)` returning FIRSTPARTY here but
+# THIRDPARTY when the exact same import is checked from the repo root.
+known_third_party = ["mcp"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["."]
+asyncio_mode = "auto"
+asyncio_default_fixture_loop_scope = "function"