Reproducibility logging and rule enforcement MCP server for scientific computing
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"repro-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# repro-mcp An MCP server that brings reproducibility logging to AI-assisted scientific computing. Git records *what* changed. `repro-mcp` records *why* — logging prompts, responses, methodological decisions, and environment snapshots to human-readable markdown files that live alongside your code. Built for researchers working under privacy or funding constraints who run models locally and need an audit trail that holds up to peer review. --- ## Why this exists AI coding assistants are increasingly used in scientific workflows, but the interaction between a researcher and an AI — the prompts, the reasoning, the alternatives considered — disappears when the session ends. This matters because: - A methods section can't cite a conversation - A future collaborator can't reproduce your reasoning, only your code - Environment drift silently breaks analyses months later `repro-mcp` captures all of this locally. No cloud dependency. No data leaves the machine. --- ## How it works `repro-mcp` is a [Model Context Protocol](https://modelcontextprotocol.io) server. Any MCP-compatible AI client (Claude Code, Cline, Cursor, Continue) can connect to it. It exposes tools the AI can call to: - Open a session and snapshot the environment - Log each prompt/response exchange - Record significant decisions and the alternatives that were rejected - Check code against reproducibility rules before it runs - Close the session with a git diff summary All output goes to `.repro/` in your project directory — plain markdown, git-friendly, human-readable. --- ## Installation Requires Python 3.11+. The recommended way is via [`uv`](https://docs.astral.sh/uv/): ```bash # No install step — uvx runs it in an isolated environment uvx repro-mcp ``` Or with pip: ```bash pip install repro-mcp ``` Or from source: ```bash git clone https://github.com/ABindoff/repro-mcp.git cd repro-mcp pip install -e . ``` --- ## Configuration ### Claude Code Add it manually to `.mcp.json` in you…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.