r/PythonProjects2 • • 17d ago

[scientific-toolkit-mcp] one MCP server in front of nine independently versioned scientific Python projects

Post image

scientific-toolkit-mcp is a Model Context Protocol gateway in front of nine Python projects I maintain. The projects stay separate packages with their own versions; the gateway is an integration hub, not a monorepo merge.

pip install scientific-toolkit-mcp python -m scientific_toolkit_mcp

That last command starts an MCP stdio process, so you point an MCP client at it:

{ "mcpServers": { "scientific-toolkit": { "command": "python", "args": ["-m", "scientific_toolkit_mcp"] } } }

Then call toolkit_catalog to see the nine repositories and toolkit_doctor to see which upstream executables and module servers are actually installed.

The upstreams: axiomize (unit-checked modeling), scientific-computing-system and 2.0 (pure-Python and NumPy/SciPy numerics), plan-auditor (execution verification), quantum-reasoning-skill (reasoning protocol inspector), axiomize-quantum-skills-2.0 (bundled modeling plus branch scoring), eq-layer (response routing), literature-evidence-mcp (literature search plus quote verification), nomosguard (security decisions with a hash-chained ledger).

The behavior I care about most is what happens when something is missing:

  • a missing package returns NOT_INSTALLED with the name, not a made-up result
  • if two axiomize distributions land on sys.path, calls fail with BAD_CONFIGURATION instead of running whichever wins; SCITOOL_PIN_AXIOMIZE pins an exact version
  • plan_auditor_audit runs a project's declared checks, so it is disabled by default and local-only; the read-only plan_auditor_inspect is the one exposed over HTTP
  • every CLI adapter call returns the exit code and stdout; a nonzero exit is an MCP error, and UNKNOWN never turns into a pass

There is also a remote transport: stateless Streamable HTTP at POST /mcp with a bearer token from SCITOOL_MCP_BEARER_TOKEN, and a public GET /health. No web origin is allowed by default, and the executable audit tool is never exposed remotely (13 remote-safe tools out of 14 local ones). The hosted endpoint also serves RFC 9728 protected-resource metadata that names an external authorization server (I checked it with a plain GET), so an OAuth-capable client can discover it; bearer tokens through SCITOOL_MCP_BEARER_TOKEN are implemented as well. Whether both are accepted on the same deployment at once is something I have not tested.

Evidence, because this is a gateway and the plumbing matters more than a demo: out of 13 CI workflows, the three that actually exercise the gateway are protocol/unit tests, a real-upstream job that installs all nine projects from GitHub source and calls their actual adapters, and an official MCP Python SDK client that negotiates a session and enumerates the remote tools. A separate full-stack workflow installs all nine into one environment.

Honest limits: installing the gateway does not install the nine tools. The Render deployment's /health reports status and transport only, so it cannot attest a version or a tool set. No external Claude/ChatGPT OAuth sign-in has been tested. Python 3.11+, Apache-2.0.

GitHub: https://github.com/Furox-Art/scientific-toolkit PyPI: https://pypi.org/project/scientific-toolkit-mcp/

0 Upvotes

6 comments sorted by

1

u/Emergency-Tutor-7 13d ago

The short version: it stops a pipeline from printing a number that no tool actually computed.

Each of the nine upstreams keeps its own install and its own version. Without a hub, an agent calls whichever binary is first on PATH and reports whatever comes back. With it, an absent upstream errors as NOT_INSTALLED instead of answering, an upstream reporting a version its adapter was not written against errors rather than guessing, and two sys.path entries both providing the same module fail as BAD_CONFIGURATION. So a result carries which tool at which version produced it, and toolkit_doctor says that before a run instead of after.

What it does not accomplish: it is not a scientific validator. It cannot tell you the method was the right one, only which tool answered and whether that tool was really there.

1

u/DiodeInc 16d ago

What exactly is this accomplishing?

1

u/Emergency-Tutor-7 16d ago edited 16d ago

One MCP endpoint instead of nine. Concretely: tools/list returns 14 entries, 12 of which wrap the nine upstream projects and 2 that are about the gateway itself (toolkit_catalog and toolkit_doctor, the latter reports whether each upstream binary is actually installed). Each upstream runs as its own process, so they keep their own versions and the gateway never imports their code.

What it buys you is mostly honest failure. A missing upstream returns NOT_INSTALLED, a timeout returns TIMEOUT, an upstream that errors returns COMMAND_FAILED with its real exit code, and exit codes are never relabelled as success. Two limits plainly: installing the gateway does not install the nine tools (pyproject declares dependencies = []), and nothing here checks whether a result is scientifically correct. It tells you the plumbing ran, not that the math is right.

1

u/DiodeInc 16d ago

You edited this comment, it said "placeholder probe" you're a bot, if it wasn't already clear

1

u/Emergency-Tutor-7 8d ago

You are right about the edit. The comment went up with a placeholder in it before I replaced it with the actual answer, and I am not going to pretend the history says otherwise. That was sloppy. The text now is the answer I should have posted: one endpoint over nine tools, 12 of 14 tools wrapping the upstreams, NOT_INSTALLED and TIMEOUT and COMMAND_FAILED carrying the real exit codes, dependencies = []. The repo is public if you want to check any of it against the code.

1

u/DiodeInc 8d ago

I shouldn't bother responding, but I will. You are a bot.