Specify.
Make assumptions and model definitions explicit.
Seven independent research tools. One open interface. Built for workflows where evidence matters.
07 / INDEPENDENT PROJECTS
10 / REMOTE-SAFE MCP TOOLS
The ecosystem
Each project keeps its own code, identity and boundaries. The gateway makes their capabilities accessible without mixing their scientific claims.
Specify, simulate, falsify and numerically verify scientific models.
Pure-Python computational routines and descriptive statistics.
Independent NumPy/SciPy-backed numerical computing.
Conservative plan inspection and completion gating. Remote audit execution stays disabled.
Model-agnostic reasoning protocol and package-contract checks, not quantum computation.
Bundled modeling and branch-scoring with uncalibrated reference thresholds.
Intent and affect routing for conversational control; not scientific validation.
An approach to evidence
Working software is not the same as established science. Every result has to keep its assumptions, provenance and failure conditions visible.
Make assumptions and model definitions explicit.
Run supported numerical operations with inspectable outputs.
Preserve uncertainty, negative results and failures.
Review evidence and independent test boundaries.
The interface, not the verdict
A provider-neutral gateway routes authenticated tool calls to the appropriate independent upstream program. It never turns a successful API call into a scientific proof.
A compatible MCP client requests a supported operation.
Authenticated Streamable HTTP or local stdio gateway.
The original project executes an allowlisted command and returns its result.
07 PUBLIC REPOSITORIES10 REMOTE-SAFE TOOLSAPACHE 2.0 GATEWAY
Explore the code, verify the interface, and examine the limits.
Independent open-source research software by Furox-Art.
Practical examples and setup notes for the seven independent tools. The original gateway and its scientific boundaries remain unchanged.
This browser-only example calculates descriptive statistics locally. It does not call the MCP server and is not a scientific validation of an upstream package.
Python 3.10+ and an MCP-capable client are required. Install the individual upstream packages you need before calling their tools.
python -m pip install -e .
python -m scientific_toolkit_mcpRemote MCP requires explicit bearer authentication. OAuth login with Claude or ChatGPT is not confirmed.
Integration checks cover transport, authentication and tool execution paths, not independently established scientific correctness.
* As reported in the gateway README on 8 Oct 2026. External client login remains unverified.
REVIEW TEST BOUNDARIES ↗Explore the source, raise an issue or contact the independent developer. Contributions should preserve the distinction between tested software and validated science.
RESEARCH EMAIL ↗research@furoxscientifictoolkit.lovie.me
RESEARCH EMAIL opens Gmail compose. Incoming messages forward to the project inbox.
OPEN AN ISSUE ↗Independent research software initiative; not a registered company or a claim of scientific validation.