Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.hxckya/pkgtruth

NPM · PKGTRUTH · SCANNED SEP 21

Catches hallucinated and slopsquatted npm and PyPI packages before an agent installs them.

Available components

npm · pkgtruth 91
+3 this week 91 Trust /100
Trust breakdown (7 categories)

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 & 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 11 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 Management70
  • Stability observed for 21 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
  • 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
Install

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

# add to Claude Code
claude mcp add hxckya-pkgtruth -- npx -y pkgtruth
// .cursor/mcp.json
{
  "mcpServers": {
    "hxckya-pkgtruth": {
      "command": "npx",
      "args": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hxckya-pkgtruth": {
      "command": "npx",
      "args": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hxckya-pkgtruth -- npx -y pkgtruth
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hxckya-pkgtruth": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pkgtruth"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hxckya-pkgtruth --command npx --arg -y --arg pkgtruth
# ~/.hermes/config.yaml
mcp_servers:
  hxckya-pkgtruth:
    command: "npx"
    args: ["-y", "pkgtruth"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hxckya-pkgtruth": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hxckya-pkgtruth -t stdio -c npx -a -y pkgtruth
// mcp.json
{
  "mcpServers": {
    "hxckya-pkgtruth": {
      "command": "npx",
      "args": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
Changelog

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 Sept 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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
  • 10 Sept 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.30 → unverified ▼ security
    • Provenance: pass → fail ▼ security
    • The attested source repository moved: hxckya/pkgtruth security
    • Schema quality: 82 → 103 ▼ functional
    • Dependency health: 0.84 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Security disclosure: fail → pass ▲ functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.2 → 0.2.2 functional
    • Package version: 0.1.2 → 0.2.1 functional
    • Package version: 0.1.2 → 0.1.3 functional
  • 8 Sept 26 +4
    • Stability: unverified → 0.27 ▲ functional
Diagnostics

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 Sept 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 https://slsa.dev/provenance/v1
Subject digest sha512:e962f0fd5f830542896e77b09a35176bcfb9a3f7884bd012bf5bf22ea9085d6672af5f978117e3400e3b5aab48da921e75873744d61cbb0e1248eb7a0

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 →

MCP tools · 3 exposed · ~519 tokens

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 →

Tool Tokens
check_dependencies ~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.

NameTypeReqDescription
ecosystemstring–Registry to check against. Default npm.
namesarrayyesPackage names to verify (max 50), without version suffixes.
NameTypeReqDescription
blockingintegeryesHow many results are HALLUCINATED or DANGER.
resultsarrayyesSorted worst-first.
totalintegeryes–

No examples provided.

check_install_command ~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.

NameTypeReqDescription
commandstringyesThe exact shell command about to run, e.g. "npm install express crossenv" or "pip install -U requests".
cwdstring–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.
NameTypeReqDescription
blockingintegeryesHow many results are HALLUCINATED or DANGER.
commandstringyes–
packagesarrayyesWhat was recognised, per install command.
resultsarrayyesSorted worst-first.
totalintegeryes–

No examples provided.

check_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.

NameTypeReqDescription
ecosystemstring–Registry to check against. Default npm.
namestringyesExact package name as it would be installed, e.g. "express", "@scope/pkg", or for PyPI "requests". No version suffix.
NameTypeReqDescription
ageDaysnumber|null–Days since first publish.
completeboolean–false when a check could not run (rate limit, outage); such a result is UNKNOWN unless already DANGER.
didYouMeanarray–For HALLUCINATED names: real packages with a similar name.
ecosystemstringyes–
existsboolean|null––
namestringyes–
pointsTostring|null–The package this one's own deprecation notice tells users to install instead, if any.
repositorystring|null––
scorenumber|null–0–100 risk score behind the verdict; null when the registry was unreachable.
signalsarrayyes–
summarystringyesOne-paragraph explanation with the suggested real package when there is one.
verdictstringyesHALLUCINATED: no such package. DANGER: do not install as-is. CAUTION: review first. UNKNOWN: could not verify — never treat as safe. SAFE: nothing found.
versionstring|null–Latest published version.
weeklyDownloadsnumber|null––

No examples provided.

Common questions

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 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 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 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.