Graneth
NPM · @GRANETH/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20
Pre-flight check for AI coding agents: hallucinated packages + secrets, 6 ecosystems, no account.
Available components
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 452 tokens (~226/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the Graneth MCP server?
Graneth runs locally as an npm package, launched with npx -y @graneth/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @graneth/mcp-server
claude mcp add com-graneth-mcp-server -- npx -y @graneth/mcp-server
{
"mcpServers": {
"com-graneth-mcp-server": {
"command": "npx",
"args": [
"-y",
"@graneth/mcp-server"
]
}
}
} {
"servers": {
"com-graneth-mcp-server": {
"command": "npx",
"args": [
"-y",
"@graneth/mcp-server"
]
}
}
} codex mcp add com-graneth-mcp-server -- npx -y @graneth/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-graneth-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@graneth/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-graneth-mcp-server --command npx --arg -y --arg @graneth/mcp-server
mcp_servers:
com-graneth-mcp-server:
command: "npx"
args: ["-y", "@graneth/mcp-server"] {
"McpServers": {
"com-graneth-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@graneth/mcp-server"
]
}
}
} assistant mcp add com-graneth-mcp-server -t stdio -c npx -a -y @graneth/mcp-server
{
"mcpServers": {
"com-graneth-mcp-server": {
"command": "npx",
"args": [
"-y",
"@graneth/mcp-server"
]
}
}
} 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.
- 19 Sept 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.
- 17 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.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 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.
- 10 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.
- 8 Sept 26 −3
- Stability: pass → 0.80 functional
- 7 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@graneth/mcp-server@0.7.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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
pre_flight_check ~242
Security pre-flight check for local file changes BEFORE committing. Run this whenever you are about to suggest `git commit`, `git push`, or open a pull request — especially when changes add package imports or dependencies (package.json / requirements.txt / Cargo.toml / go.mod / Gemfile / composer.json / import statements) or could contain secrets. Detects AI-hallucinated (non-existent) packages by live-checking six registries (npm, PyPI, crates.io, RubyGems, Go module proxy, Packagist) plus a bundled public threat-feed snapshot, which keeps catching a known hallucinated name even after an attacker registers it; risk-scores dependencies an AI agent introduced by compounding metadata signals (new + install-scripts + low-adoption + no-provenance = an attack shape no single check flags); and finds hardcoded credentials via pattern + entropy analysis. Always free, no account required. Returns CLEAR, REVIEW_REQUIRED, or BLOCKED with specific findings and remediation.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | What these changes do (helps triage) |
| files | array | yes | Files staged for commit (path + content) |
No output schema declared.
No examples provided.
report_hallucination ~210
Report an AI-hallucinated package name to Graneth's public threat feed, so every user's pre-flight catches it — permanently, even if an attacker registers the name later. IMPORTANT: only call this AFTER the human has explicitly agreed to report the name; ask them first. Sends exactly one package name + ecosystem to graneth.com (never file contents). The server re-verifies non-existence against the live registry before accepting. Reportable ecosystems: npm (unscoped), pypi, crates, gems — namespaced names (npm @scope, go, composer) are rejected to keep internal package names out of a public feed. Optional `reporter` is a public attribution handle shown on the feed entry.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Registry the name was checked against |
| package | string | yes | The hallucinated package name (as caught by pre_flight_check) |
| reporter | string | – | Optional public attribution handle ([a-zA-Z0-9_-]) |
No output schema declared.
No examples provided.
What is the Graneth MCP server?
Graneth is an MCP server listed in the public MCP registry as com.graneth/mcp-server. Pre-flight check for AI coding agents: hallucinated packages + secrets, 6 ecosystems, no account. This page covers its npm package (@graneth/mcp-server).
Is the Graneth MCP server safe to use?
Graneth scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Graneth MCP server expose?
Graneth exposes 2 tools: pre_flight_check, report_hallucination. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.
Is the Graneth MCP server still maintained?
Graneth is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Graneth MCP server under?
Graneth declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.