GridProof
NPM · GRIDPROOF
Gridproof your UI — automated spacing & grid QA in the agent loop (MCP server).
Available components
Last scanned (17 hours ago)
Scores higher than 83% 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 63 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 485 tokens (~121/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 4 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 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 −2
- Security disclosure: fail → unverified ▼ functional
- 8 Oct 26 −1
- Stability: pass → 0.93 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 16 Oct 2026 · Analysed npm/gridproof@0.1.3
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
gp_audit Gridproof: audit a URL ~145
Render a running frontend and audit its spacing/grid geometry against the spacing-scale and arbitrary-value rules. Returns a structured AuditReport (violations with fix hints) plus a text summary.
| Name | Type | Req | Description |
|---|---|---|---|
| maxViolations | integer | – | Cap report size to protect agent context window. |
| rules | array | – | Subset of rules to run. Default: all enabled in config. |
| selector | string | – | Limit audit to a DOM subtree, e.g. '#main'. Default: body. |
| url | string | yes | URL of the running frontend, e.g. http://localhost:5173 |
| viewport | object | – | Viewport for this audit pass. Run once per breakpoint. |
No output schema declared.
No examples provided.
gp_check_element Gridproof: re-check one element ~97
Re-check a single element's subtree after a fix, without re-running the full audit. Returns the violations found under that selector.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS selector of the single element (subtree) to re-check. |
| url | string | yes | URL of the running frontend, e.g. http://localhost:5173 |
| viewport | object | – | Viewport for this check. Defaults to 1440×900. |
No output schema declared.
No examples provided.
gp_get_config Gridproof: get resolved config ~71
Return the effective Gridproof configuration (defaults merged with gridproof.config.json if present): baseUnit, allowedValues, canonicalSizes, minTapTarget, rule severities, suppressions.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Directory to search upward from for gridproof.config.json. Defaults to the server's working directory. |
No output schema declared.
No examples provided.
gp_report Gridproof: audit + write HTML report ~172
Render a URL, audit its spacing/grid geometry, and WRITE a self-contained HTML report to disk (default ./gridproof-report.html). Returns the file path plus the same AuditReport JSON as gp_audit.
| Name | Type | Req | Description |
|---|---|---|---|
| maxViolations | integer | – | Cap report size to protect agent context window. |
| outputPath | string | – | Where to write the HTML report. Default: ./gridproof-report.html |
| rules | array | – | Subset of rules to run. Default: all enabled in config. |
| selector | string | – | Limit audit to a DOM subtree, e.g. '#main'. Default: body. |
| url | string | yes | URL of the running frontend, e.g. http://localhost:5173 |
| viewport | object | – | Viewport for this audit pass. Run once per breakpoint. |
No output schema declared.
No examples provided.
How do I install the GridProof MCP server?
GridProof runs locally as an npm package, launched with npx -y gridproof. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · gridproof
claude mcp add gridproof-gridproof -- npx -y gridproof
What is the GridProof MCP server?
GridProof is an MCP server listed in the public MCP registry as io.github.gridproof/gridproof. Gridproof your UI, automated spacing & grid QA in the agent loop (MCP server). This page covers its npm package (gridproof).
Is the GridProof MCP server safe to use?
GridProof scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 GridProof MCP server expose?
GridProof exposes 4 tools: gp_audit, gp_check_element, gp_get_config, gp_report. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.
Is the GridProof MCP server still maintained?
GridProof is still listed as active in the MCP registry. We last reached this channel on 16 October 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 GridProof MCP server under?
GridProof declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.