stackcheck
PYPI · STACKCHECK-MCP
Latest stable npm/PyPI/Maven versions plus the incompatibilities between them.
Available components
Last scanned (12 hours ago)
Scores higher than 63% of PyPI servers
Category Developer Tools
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 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 (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 399 tokens (~133/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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.
- 21 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 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 21 Nov 2026 · Analysed pypi/stackcheck-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 | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| 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_stack ~161
Latest stable versions plus incompatibilities between the packages and their shared deps (peer deps, requires_dist, engines, requires_python, wheels, BOM). Example: {"npm": ["react", "typescript", "typescript-eslint", "vite@^8"], "pypi": ["fastapi"]}
| Name | Type | Req | Description |
|---|---|---|---|
| maven | array | – | group:artifact[:version|range] |
| maven_bom | string | – | BOM group:artifact[:version] |
| npm | array | – | name or name@range |
| pypi | array | – | PEP 508, extras ok |
| runtimes | array | – | endoflife slugs |
| targets | – | – | cycle or version; default Node LTS, newest Python, Java LTS |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | object | – | – |
| issues | array | – | – |
| maven | object | – | – |
| npm | object | – | – |
| pypi | object | – | – |
| runtimes | object | – | – |
| stale | boolean | – | – |
| targets | object | – | – |
| validation | object | – | – |
| warnings | object | – | – |
No examples provided.
explain_issue ~109
Declared peer deps/engines (npm), requires_dist/requires_python (PyPI) or parent and dependencies (Maven) of one version, to dig into an issue. Example: {"ecosystem": "npm", "package": "typescript-eslint", "version": "8.72.1"}
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | – |
| package | string | yes | npm name, PyPI name[extras], group:artifact |
| version | string | – | default: latest stable |
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | array | – | – |
| deprecated | string | – | – |
| ecosystem | string | yes | – |
| engines | object | – | – |
| error | string | – | – |
| extras | array | – | – |
| optionalPeers | array | – | – |
| package | string | yes | – |
| parent | string | – | – |
| peerDependencies | object | – | – |
| requires_dist | array | – | – |
| requires_python | string | – | – |
| stale | boolean | – | – |
| version | string | – | – |
| yanked | string | – | – |
No examples provided.
get_runtime_info ~82
Latest, LTS (lts_eol: true if that LTS is end-of-life), next LTS, maintained cycles and EOL date of the recommended cycle, from endoflife.date. Example: {"products": ["nodejs", "python", "eclipse-temurin"]}
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | endoflife.date slugs |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | object | – | – |
| runtimes | object | – | – |
| stale | boolean | – | – |
No examples provided.
How do I install the stackcheck MCP server?
stackcheck runs locally as a PyPI package, launched with uvx stackcheck-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · stackcheck-mcp
claude mcp add titouannnn-stackcheck-mcp -- uvx stackcheck-mcp
What is the stackcheck MCP server?
stackcheck is an MCP server listed in the public MCP registry as io.github.titouannnn/stackcheck-mcp. Latest stable npm/PyPI/Maven versions plus the incompatibilities between them. This page covers its PyPI package (stackcheck-mcp).
Is the stackcheck MCP server safe to use?
stackcheck scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 stackcheck MCP server expose?
stackcheck exposes 3 tools: check_stack, get_runtime_info, explain_issue. Their descriptions and schemas cost roughly 352 tokens of context every time the server is loaded.
Is the stackcheck MCP server still maintained?
stackcheck is still listed as active in the MCP registry. We last reached this channel on 21 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 stackcheck MCP server under?
stackcheck declares the Apache-2.0 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 stackcheck MCP server?
VerifyMCP ran 15 checks on stackcheck, 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 stackcheck: 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 a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.