forall-mcp
Forall (∀) is a coding harness from Astrio that helps developers build correct software by generating spec-driven code alongside machine-checkable proofs.
Runssource: GitHubRustApache-2.0commit 804ec8000347
Rust, Apache-2.0 licensed. The project labels itself: agent framework, agent orchestration, java, rust and typescript.
forall-mcp runs. An Argusic agent installed it in 0.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Rust workspace builds with cargo, all 44 unit/integration tests pass, and the npm MCP bridge correctly proxies MCP tool requests between stdio and Streamable HTTP.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- under a minute
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test: 44 passed (28+12+1+3+0+0); npm @astrio/forall-mcp mocked end-to-end: bridge proxied tools/list and returned correct tool definitions
- Model tokens used
- 101,060
- Exact commit tested
- 804ec8000347
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here's my final assessment: **Rust workspace** — cargo build and cargo test both succeed cleanly. ``` test result: ok. 28 passed (forall-authoring) test result: ok. 12 passed (forall-hosted-verify) test result: ok. 1 passed (standalone_flow integration test) test result: ok. 3 passed (wire_conformance tests) test result: ok. 0 passed (forall-wire unit tests — no tests in that crate) test result: ok. 0 passed (forall-wire doc-tests) ``` **npm MCP bridge** — `@astrio/forall-mcp` installs, syntax-checks OK, module imports cleanly, and t… **No errors encountered** during install, build, test, or verification.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.5 minutes, faster than the median of the 38 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 39 agent-framework projects Argusic has installed and timed, forall-mcp was the 3rd fastest to reach a running state, and 28 of 39 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.5 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/forall-mcp)Questions
- Does forall-mcp run?
- Yes. forall-mcp runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test forall-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 804ec8000347. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test forall-mcp?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does forall-mcp take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does forall-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing forall-mcp?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does forall-mcp compare with the alternatives?
- Of the 39 agent-framework projects Argusic has installed and timed, forall-mcp was the 3rd fastest to reach a running state, and 28 of 39 reached one at all.
- Where is the evidence for forall-mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.