# io.github.hxckya/pkgtruth (npm · pkgtruth)

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

- Trust score: 91/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `pkgtruth`: 91/100 (this document), [markdown](https://verifymcp.io/servers/hxckya-pkgtruth/pkgtruth.md), [page](https://verifymcp.io/servers/hxckya-pkgtruth/pkgtruth)

## Channel facts

- Registry: `npm`
- Package: `pkgtruth`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to hxckya/pkgtruth).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add hxckya-pkgtruth -- npx -y pkgtruth
```

### Cursor

```json
{
  "mcpServers": {
    "hxckya-pkgtruth": {
      "command": "npx",
      "args": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hxckya-pkgtruth": {
      "command": "npx",
      "args": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hxckya-pkgtruth --command npx --arg -y --arg pkgtruth
```

### Hermes

```yaml
mcp_servers:
  hxckya-pkgtruth:
    command: "npx"
    args: ["-y", "pkgtruth"]
```

### Netclaw

```json
{
  "McpServers": {
    "hxckya-pkgtruth": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hxckya-pkgtruth -t stdio -c npx -a -y pkgtruth
```

### Other

```json
{
  "mcpServers": {
    "hxckya-pkgtruth": {
      "command": "npx",
      "args": [
        "-y",
        "pkgtruth"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 91, +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.

### 2026-09-19 (score 90, +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.

### 2026-09-16 (score 89, +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.

### 2026-09-14 (score 88, +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.

### 2026-09-12 (score 87, +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.

### 2026-09-11 (score 86, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.84

### 2026-09-10 (score 75, −11)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.30 → unverified
- [security regression] Provenance: pass → fail
- [security] The attested source repository moved: hxckya/pkgtruth
- [functional regression] Schema quality: 82 → 103
- [functional regression] Dependency health: 0.84 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: pass → fail
- [functional improvement] 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

### 2026-09-08 (score 86, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (3)

### `check_package` (~162 tokens)

Check one package

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.

Input parameters:

- `ecosystem` (string): Registry to check against. Default npm.
- `name` (string, required): Exact package name as it would be installed, e.g. "express", "@scope/pkg", or for PyPI "requests". No version suffix.

Output parameters:

- `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)
- `exists` (boolean|null)
- `name` (string)
- `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)
- `summary` (string): One-paragraph explanation with the suggested real package when there is one.
- `verdict` (string): 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)

### `check_dependencies` (~118 tokens)

Gate a whole dependency list

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.

Input parameters:

- `ecosystem` (string): Registry to check against. Default npm.
- `names` (array, required): Package names to verify (max 50), without version suffixes.

Output parameters:

- `blocking` (integer): How many results are HALLUCINATED or DANGER.
- `results` (array): Sorted worst-first.
- `total` (integer)

### `check_install_command` (~239 tokens)

Check the packages an install command would fetch

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.

Input parameters:

- `command` (string, required): 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.

Output parameters:

- `blocking` (integer): How many results are HALLUCINATED or DANGER.
- `command` (string)
- `packages` (array): What was recognised, per install command.
- `results` (array): Sorted worst-first.
- `total` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/hxckya-pkgtruth/pkgtruth#diagnostics

## Score history

- 2026-09-21: 91
- 2026-09-20: 90
- 2026-09-19: 90
- 2026-09-18: 89
- 2026-09-17: 89
- 2026-09-16: 89
- 2026-09-15: 88
- 2026-09-14: 88
- 2026-09-13: 87
- 2026-09-12: 87
- 2026-09-11: 86
- 2026-09-10: 75
- 2026-09-09: 86
- 2026-09-08: 86
- 2026-09-07: 82
- 2026-09-06: 82
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 82
- 2026-09-02: 82
- 2026-09-01: 82
- 2026-08-31: 82

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

## Links

- npm package: https://www.npmjs.com/package/pkgtruth
- Socket report: https://socket.dev/npm/package/pkgtruth
- Repository: https://github.com/hxckya/pkgtruth
- Changelog RSS feed: https://verifymcp.io/servers/hxckya-pkgtruth/pkgtruth.xml
- Changelog JSON feed: https://verifymcp.io/servers/hxckya-pkgtruth/pkgtruth.json
- HTML version of this page: https://verifymcp.io/servers/hxckya-pkgtruth/pkgtruth