io.github.hxckya/pkgtruth
NPM · PKGTRUTH
Catches hallucinated and slopsquatted npm and PyPI packages before an agent installs them.
Available components
Last scanned (9 hours ago)
Scores higher than 98% of npm servers
Category Security
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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hxckya/pkgtruth). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 56 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 519 tokens (~173/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- 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 3 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 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.
- 30 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 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.
- 14 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.
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/pkgtruth@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | hxckya/pkgtruth |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/hxckya/pkgtruth/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 2779070428 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e962f0fd5f830542896e77b09a35176bcfb9a3f7884bd012bf5bf22ea9085d6672af5f978117e3400e3b5aab48da921e75873744d61cbb0e1248eb7a0 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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_dependencies Gate a whole dependency list ~118
Verify many npm or PyPI packages at once — use this before writing a package.json or requirements.txt, or handing a dependency list to a user. All names must belong to one ecosystem per call. Results are sorted worst-first so anything hallucinated or dangerous surfaces at the top. Read-only; batches registry requests and caches adoption figures, so 50 names take a few seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Registry to check against. Default npm. |
| names | array | yes | Package names to verify (max 50), without version suffixes. |
| Name | Type | Req | Description |
|---|---|---|---|
| blocking | integer | yes | How many results are HALLUCINATED or DANGER. |
| results | array | yes | Sorted worst-first. |
| total | integer | yes | – |
No examples provided.
check_install_command Check the packages an install command would fetch ~239
Verify the packages a shell command would install or execute, before running it: `npm install …`, `npx …`, `pnpm add`, `yarn add`, `bun add`, `pip install`, `uv add`, `poetry add` and similar, including behind `sudo`, `&&` chains and `sh -c`. Extracts the package names (npm and PyPI at once), checks each against its registry, and returns them worst-first. A command that installs nothing by name (a bare `npm install` from a lockfile, `git`, `npm test`, or `npx <bin>` of a tool already in node_modules) returns total 0 and costs no network call — use check_dependencies on the manifest in that case. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The exact shell command about to run, e.g. "npm install express crossenv" or "pip install -U requests". |
| cwd | string | – | Directory the command will run in. Lets "npx <bin>" of an already-installed tool be recognised as fetching nothing. Defaults to the server's working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| blocking | integer | yes | How many results are HALLUCINATED or DANGER. |
| command | string | yes | – |
| packages | array | yes | What was recognised, per install command. |
| results | array | yes | Sorted worst-first. |
| total | integer | yes | – |
No examples provided.
check_package Check one package ~162
Verify a single npm or PyPI package before installing, importing, or recommending it. Returns whether it actually exists, and flags slopsquatting (a low-adoption package impersonating a popular one), names npm removed for malware, install-time scripts, deprecation, and abandonment. Call this whenever you are about to introduce a dependency you have not verified in this session. Read-only; one or two requests to the public registry. A verdict of UNKNOWN means the registry did not answer — retry, never assume safe.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Registry to check against. Default npm. |
| name | string | yes | Exact package name as it would be installed, e.g. "express", "@scope/pkg", or for PyPI "requests". No version suffix. |
| Name | Type | Req | Description |
|---|---|---|---|
| ageDays | number|null | – | Days since first publish. |
| complete | boolean | – | false when a check could not run (rate limit, outage); such a result is UNKNOWN unless already DANGER. |
| didYouMean | array | – | For HALLUCINATED names: real packages with a similar name. |
| ecosystem | string | yes | – |
| exists | boolean|null | – | – |
| name | string | yes | – |
| pointsTo | string|null | – | The package this one's own deprecation notice tells users to install instead, if any. |
| repository | string|null | – | – |
| score | number|null | – | 0–100 risk score behind the verdict; null when the registry was unreachable. |
| signals | array | yes | – |
| summary | string | yes | One-paragraph explanation with the suggested real package when there is one. |
| verdict | string | yes | HALLUCINATED: no such package. DANGER: do not install as-is. CAUTION: review first. UNKNOWN: could not verify — never treat as safe. SAFE: nothing found. |
| version | string|null | – | Latest published version. |
| weeklyDownloads | number|null | – | – |
No examples provided.
How do I install the io.github.hxckya/pkgtruth MCP server?
io.github.hxckya/pkgtruth runs locally as an npm package, launched with npx -y pkgtruth. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pkgtruth
claude mcp add hxckya-pkgtruth -- npx -y pkgtruth
What is the io.github.hxckya/pkgtruth MCP server?
io.github.hxckya/pkgtruth is an MCP server listed in the public MCP registry as io.github.hxckya/pkgtruth. Catches hallucinated and slopsquatted npm and PyPI packages before an agent installs them. This page covers its npm package (pkgtruth).
Is the io.github.hxckya/pkgtruth MCP server safe to use?
io.github.hxckya/pkgtruth scores 95 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. Its build provenance is signed and verified. 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.hxckya/pkgtruth MCP server expose?
io.github.hxckya/pkgtruth exposes 3 tools: check_package, check_dependencies, check_install_command. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.
Is the io.github.hxckya/pkgtruth MCP server still maintained?
io.github.hxckya/pkgtruth 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.hxckya/pkgtruth MCP server under?
io.github.hxckya/pkgtruth 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.hxckya/pkgtruth MCP server?
VerifyMCP ran 16 checks on io.github.hxckya/pkgtruth, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.