io.github.vschernoff/forge-test-mcp
NPM · FORGE-TEST-MCP
Runs Foundry tests and builds; returns compact, structured failures to AI coding agents
Available components
Last scanned (13 hours ago)
Scores higher than 39% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 526 tokens (~175/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/forge-test-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build ~96
Compile the project with `forge build` and return compiler errors and warnings as structured items (file, line, column, code, message). Unchanged files are not recompiled and forge does not repeat their warnings; pass force: true to recompile everything.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Recompile everything, so warnings for unchanged files are reported again. |
| max_bytes | integer | – | Response size budget in bytes (default 8192). |
No output schema declared.
No examples provided.
explain_failure ~129
Re-run one test at high verbosity and return only that test: its reason, decoded call trace (trimmed to the path to the revert when long), backtrace, logs and, for fuzz or invariant tests, the counterexample. Pass the test name as run_tests reports it, e.g. "BankTest.test_transfer()".
| Name | Type | Req | Description |
|---|---|---|---|
| contract | string | – | Test contract, if not given in `test`. |
| max_bytes | integer | – | Response size budget in bytes (default 8192). |
| test | string | yes | Test function, optionally with its contract: "Contract.test_name()". |
No output schema declared.
No examples provided.
run_tests ~204
Run `forge test` and return a compact summary: counts, and for each failing test its kind (unit, fuzz, invariant, setup), decoded reason, fuzz counterexample or invariant call sequence, and console logs. isError means the tests did not run (compile error, no matching tests, timeout, missing forge, …); never report that as passing.
| Name | Type | Req | Description |
|---|---|---|---|
| fuzz_runs | integer | – | Override fuzz runs. A value below the project setting is reported as reduced; do not use it to make tests pass. |
| match_contract | string | – | Only run test contracts matching this regex. |
| match_path | string | – | Only run test files matching this glob. |
| match_test | string | – | Only run test functions matching this regex. |
| max_bytes | integer | – | Response size budget in bytes (default 8192). |
| traces | boolean | – | Attach a decoded trace excerpt to the first 5 failures (a second, text-mode forge run). Default true. |
No output schema declared.
No examples provided.
How do I install the io.github.vschernoff/forge-test-mcp server?
io.github.vschernoff/forge-test-mcp runs locally as an npm package, launched with npx -y forge-test-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · forge-test-mcp
claude mcp add vschernoff-forge-test-mcp -- npx -y forge-test-mcp
What is the io.github.vschernoff/forge-test-mcp server?
io.github.vschernoff/forge-test-mcp is listed in the public MCP registry as io.github.vschernoff/forge-test-mcp. Runs Foundry tests and builds; returns compact, structured failures to AI coding agents. This page covers its npm package (forge-test-mcp).
Is the io.github.vschernoff/forge-test-mcp server safe to use?
io.github.vschernoff/forge-test-mcp scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vschernoff/forge-test-mcp server expose?
io.github.vschernoff/forge-test-mcp exposes 3 tools: run_tests, explain_failure, build. Their descriptions and schemas cost roughly 429 tokens of context every time the server is loaded.
Is the io.github.vschernoff/forge-test-mcp server still maintained?
io.github.vschernoff/forge-test-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vschernoff/forge-test-mcp server under?
io.github.vschernoff/forge-test-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.vschernoff/forge-test-mcp server?
VerifyMCP ran 15 checks on io.github.vschernoff/forge-test-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.vschernoff/forge-test-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.