marcus-toolkit
The run-side toolbox that Marcus extensions share.
What this is, briefly
Marcus coordinates AI agents through a shared task board: agents pull work from the board over MCP (the Model Context Protocol, the wire protocol for Marcus's tools), do it, and report back with evidence. An extension is a separate program that seeds a board and runs agents against it for one purpose: verifying citations, verifying a numerical report, coordinating Minecraft agents, refereeing a wargame.
Every extension needs the same scaffolding around a run, and every extension so far rebuilt it. This package is that scaffolding, built once (the inventory and the reasoning are in painted-porch/marcus issue #914):
| Module | What it does |
|---|---|
marcus_toolkit.server |
a server under test: a private Marcus started for one run with every model-provider key stripped from its environment and the model switched off with an empty key, so the run can spend nothing by construction; refuses a port someone else holds and proves the port's owner is this run's server |
marcus_toolkit.seed |
seeds a project with exactly the tasks named, through create_project(options.tasks), and refuses before the call what the board would mis-handle: an unknown spec key, a build-family label, a dependency naming no task, a project name containing "test" |
marcus_toolkit.watchdog |
stops a run the moment its spend reaches the approved line; the line is re-read on every poll when it comes from a file |
marcus_toolkit.pricing, marcus_toolkit.usage |
one price table; usage rows read from pi's transcripts or from <state>/<agent>/usage.jsonl, one row per model call, which any runtime can write |
marcus_toolkit.sampler |
reads the board from outside every few seconds and applies the drain verdict's claimability rule, so frontier width has a time series |
marcus_toolkit.integrity |
hashes the files that execute, hashes the same files as committed, records a checkout's version |
marcus_toolkit.record |
the run record: runs/<stamp>/, run-config.txt, JSONL streams, copies |
marcus_toolkit.measure |
pulls and the idle-poll ratio, the kernel's frontier series, the sampler's series, board counts from a copy of kanban.db |
marcus_toolkit.client, marcus_toolkit.agent |
the MCP client and a pull-loop agent shell in Python |
node/ |
the same client in Node: mcp-http.js and board.js |
marcus_toolkit.livecheck |
the toolbox's own live check against a real Marcus checkout |
Nothing in this package imports Marcus's own code.
It talks to a server over MCP and reads the files a run leaves behind, which is all an extension may do (docs/architecture/extension-contract.md in the Marcus repository).
Install
pip install -e . # from a checkout
pip install -e ".[dev]" # with the test and lint tools
For the Node client, import node/board.js and node/mcp-http.js directly; they have no dependencies.
The live check
python -m marcus_toolkit.livecheck --checkout ~/dev/marcus --out livecheck-runs
Starts a server under test from that checkout, seeds two tasks (the second depending on the first), runs one scripted agent through register, pull, report, pull, report, drain, reads the board from outside before and after, and writes livecheck-runs/<stamp>/VERDICT.json.
It passes only when every card closed, the agent heard the drain, every reply was read back, and the server log carries no model-provider host.
CI runs it against the Marcus commit pinned in .github/workflows/ci.yml.
Where it came from
The Minecraft harness's plumbing (painted-porch/marcus-minecraft, plumbing/), the Marcus experiment runners (dev-tools/experiments/runners/marcus_client.py), and the AI-citation verifier's free rehearsal.
The defects those runs found are fixed here once: a stop line read only at process start, a placeholder key that fired one real call on startup, a task spec whose extra key broke every promotion, a blocked task counted as claimable.
Versioning
Each release states the Marcus commit it was live-checked against. The toolbox depends on Marcus's MCP tool names and reply shapes, not on its code; when those change, this package gets a release, not a patch to the kernel.
Metadata
Release files for marcus-toolkit 0.1.0
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 |
|---|---|---|---|---|
| marcus_toolkit-0.1.0.tar.gz | 54.0 kB | With provenance | Details for marcus_toolkit-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| marcus_toolkit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for marcus_toolkit-0.1.0-py3-none-any.whl |
Total release size: 116.4 kB
Release files / marcus_toolkit-0.1.0.tar.gz
| Download URL | marcus_toolkit-0.1.0.tar.gz |
|---|---|
| Size | 54.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3368e9c20eac1df13b8782875a794a93a9ae21b9de41d9a4a9a5eb75de383944
|
|
BLAKE2b-256 checksum How to use checksums |
d83cd8cfb0392d1f2f7e55d9e11bc27e81f678694740f1b59612672759f92c1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logRelease files / marcus_toolkit-0.1.0-py3-none-any.whl
| Download URL | marcus_toolkit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 62.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5dfe0c9ac84216a857cc75069f59b10e90c29a16f1b19a22122f93adc09aca5f
|
|
BLAKE2b-256 checksum How to use checksums |
ae7e30090758bead1d96739a49e47b15636a1202777549cdbf903c927aa581fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logSecurity for marcus-toolkit 0.1.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for marcus_toolkit-0.1.0.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 Nov 13, 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.