io.github.nickjlamb/groundwork
NPM · @PHARMATOOLS/GROUNDWORK
Deployment-readiness checks for document-QA and extraction AI: grounding, extraction, CI gate.
Available components
Last scanned (7 hours ago)
Scores higher than 87% 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 Security98
- 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
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
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 37 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 735 tokens (~147/item across 5 items; 5 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.90 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
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/@pharmatools/groundwork@0.4.1
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 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
check_answer_grounding Check one answer's grounding ~202
Deterministically check a single answer against the context it should be grounded in: required facts (anchors) present, every number traceable to the context, abstention when the question is unanswerable. Same logic as the CI gate — no model, no network. Returns pass/fail with named issues.
| Name | Type | Req | Description |
|---|---|---|---|
| abstain_markers | array | – | Phrases that count as a valid refusal (defaults cover common forms) |
| allowed_new_numbers | array | – | Numbers legitimately absent from the context (e.g. computed totals) |
| answer | string | yes | The answer to check |
| answer_anchors | array | – | Facts a correct answer MUST contain (with acceptable rephrasings) |
| answerable | boolean | – | false → the context cannot answer this; the only correct behaviour is abstention |
| context | string | yes | The retrieved passage(s) the answer must be grounded in |
| question | string | yes | The question that was asked |
No output schema declared.
No examples provided.
check_extraction Check one extracted record ~221
Deterministically check a structured extraction against its hand-labelled gold record: schema validity (nullable fields are the abstention contract), field accuracy with per-field normalisers (dates → ISO, money → minor units) and aliases, and fabrication — a non-null value in a field whose gold is null (a guessed date of birth the document never stated). Same logic as the CI gate — no model, no network. Returns pass/fail with named issues and a per-field verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | object | – | Per-field acceptable alternative gold values (matched after normalisation) |
| gold | object | yes | The hand-labelled gold record; null means THE DOCUMENT DOES NOT STATE IT — gold's keys define which fields are compared |
| normalize | object | – | Per-field normaliser applied to both sides before comparing |
| record | object | yes | The record the system extracted ({ field: value | null }) |
| schema | object | – | The JSON Schema the record must validate against (type a must-find field non-nullable, a may-be-absent field nullable) |
No output schema declared.
No examples provided.
check_readiness Run the readiness gate on a repo ~127
Run `groundwork check` in a repo that has a scaffolded harness: redaction self-test, then the archetype's eval (grounding for document-qa, extraction for extraction) against the repo's own gold set. Returns the exit code, the main scorer's metrics, and any named failures — exactly what CI would report.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | boolean | – | Freeze this run as the regression floor |
| ci | boolean | – | Also compare against the committed baseline and fail on regression |
| dir | string | yes | Absolute path to the repo root (the directory containing groundwork/) |
No output schema declared.
No examples provided.
cost_summary Summarise measured token costs ~57
Run `groundwork cost` in a repo: measured token usage from eval runs, with savings recommendations in leverage order (prompt caching, batching, context trimming, model routing last).
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | Absolute path to the repo root |
No output schema declared.
No examples provided.
scaffold_harness Scaffold the readiness harness into a repo ~128
Run `groundwork init [archetype]` in a repo: writes the adapter boundary, redaction config, gold-set templates, GitHub Action, and playbook for a deployment pattern — document-qa (documents → grounded answers) or extraction (documents → structured fields). Never overwrites existing files. After scaffolding, the human wires groundwork/adapter.mjs and replaces the example gold cases with real ones.
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | string | – | Deployment pattern to scaffold (default: document-qa) |
| dir | string | yes | Absolute path to the repo root to scaffold into |
No output schema declared.
No examples provided.
How do I install the io.github.nickjlamb/groundwork MCP server?
io.github.nickjlamb/groundwork runs locally as an npm package, launched with npx -y @pharmatools/groundwork. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pharmatools/groundwork
claude mcp add nickjlamb-groundwork -- npx -y @pharmatools/groundwork
What is the io.github.nickjlamb/groundwork MCP server?
io.github.nickjlamb/groundwork is an MCP server listed in the public MCP registry as io.github.nickjlamb/groundwork. Deployment-readiness checks for document-QA and extraction AI: grounding, extraction, CI gate. This page covers its npm package (@pharmatools/groundwork).
Is the io.github.nickjlamb/groundwork MCP server safe to use?
io.github.nickjlamb/groundwork scores 85 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.nickjlamb/groundwork MCP server expose?
io.github.nickjlamb/groundwork exposes 5 tools: check_answer_grounding, check_extraction, check_readiness, scaffold_harness, cost_summary. Their descriptions and schemas cost roughly 735 tokens of context every time the server is loaded.
Is the io.github.nickjlamb/groundwork MCP server still maintained?
io.github.nickjlamb/groundwork 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.nickjlamb/groundwork MCP server under?
io.github.nickjlamb/groundwork declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.