toolprint by JEStats
NPM · TOOLPRINT
package-lock.json for MCP trust: catch MCP rug-pulls, tool poisoning, and leaked secrets.
Available components
Last scanned (23 hours ago)
Scores higher than 70% 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
- 31 of 93 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 jestatsio/toolprint). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1002 tokens (~501/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 Management27
- Stability observed for 8 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 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
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.
- 23 Oct 26 +3
- Stability: unverified → 0.27 ▲ functional
- 16 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 15 Oct 26 67
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 23 Oct 2026 · Analysed npm/toolprint@0.4.1
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 | jestatsio/toolprint |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jestatsio/toolprint/.github/workflows/release.yml@refs/tags/v0.4.1 |
| Rekor log index | 3267063766 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cc69f0acad830acfb017153585503995b1d2485f830400002d9dadd2c505957f3a29e58d402a545dcf9649d53975d508f4d042a26e7f69cb6e883f1b8 |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
pin Pin current definitions into toolprint.lock ~445
Scan, then write the current capability definitions into toolprint.lock as the trusted baseline for future scans. Pinning accepts drift, so only call this after the user reviews the changes; poisoning and leaked-secret findings still set `failing: true`. The user should commit the lockfile after a pin.
| Name | Type | Req | Description |
|---|---|---|---|
| allClients | boolean | – | Discover and scan the MCP config of every agent client installed on this machine (Claude Code, Claude Desktop, Cursor, Zed, and more). |
| baseline | string | – | Path to a prior JSON report, to show findings new or resolved since then. |
| clients | array | – | Scan only these agent client ids, for example `cursor` or `zed`. |
| config | string | – | Path to an MCP client config file (Claude Desktop / VS Code / Cursor). |
| failOn | string | – | Minimum severity that counts as failing: info, low, medium, high, or critical. Default high. |
| failOnNew | boolean | – | With `baseline`, count only newly introduced findings as failing. |
| ignoreFile | string | – | Path to toolprint.ignore.json with reviewed false positives. |
| lockfile | string | – | Path to toolprint.lock (default: nearest one). |
| probe | boolean | – | Call tools the server annotates as read-only (a self-report, not verified) with empty arguments and inspect what they return. Off by default; only probe servers the user trusts to execute. |
| probeTools | array | – | Call these tools by name regardless of annotation. Enables probing on its own. |
| skills | boolean|string | – | Scan SKILL.md skill bundles on disk instead of MCP servers: `true` for the default skill roots, or a directory path. |
| target | string | – | What to scan: an MCP config path, an http(s) MCP URL, an `npx:<package>` spec, or a raw server command. Omit to auto-discover the project's MCP config. |
| timeoutMs | integer | – | Per-server timeout in milliseconds. Default 30000. |
| workingDirectory | string | – | Project directory for relative paths and lockfile discovery. Default: this process's working directory. |
No output schema declared.
No examples provided.
scan Scan MCP servers and skills ~457
Connect to MCP servers (or read skill bundles), compare every capability against toolprint.lock, and report tool-poisoning, secret-leak, and rug-pull findings. Read-only: never writes the lockfile. Findings at or above `failOn` set `failing: true` and `exitCode: 2` in the structured result.
| Name | Type | Req | Description |
|---|---|---|---|
| allClients | boolean | – | Discover and scan the MCP config of every agent client installed on this machine (Claude Code, Claude Desktop, Cursor, Zed, and more). |
| baseline | string | – | Path to a prior JSON report, to show findings new or resolved since then. |
| clients | array | – | Scan only these agent client ids, for example `cursor` or `zed`. |
| config | string | – | Path to an MCP client config file (Claude Desktop / VS Code / Cursor). |
| failOn | string | – | Minimum severity that counts as failing: info, low, medium, high, or critical. Default high. |
| failOnNew | boolean | – | With `baseline`, count only newly introduced findings as failing. |
| ignoreFile | string | – | Path to toolprint.ignore.json with reviewed false positives. |
| lockfile | string | – | Path to toolprint.lock (default: nearest one). |
| probe | boolean | – | Call tools the server annotates as read-only (a self-report, not verified) with empty arguments and inspect what they return. Off by default; only probe servers the user trusts to execute. |
| probeTools | array | – | Call these tools by name regardless of annotation. Enables probing on its own. |
| skills | boolean|string | – | Scan SKILL.md skill bundles on disk instead of MCP servers: `true` for the default skill roots, or a directory path. |
| target | string | – | What to scan: an MCP config path, an http(s) MCP URL, an `npx:<package>` spec, or a raw server command. Omit to auto-discover the project's MCP config. |
| timeoutMs | integer | – | Per-server timeout in milliseconds. Default 30000. |
| workingDirectory | string | – | Project directory for relative paths and lockfile discovery. Default: this process's working directory. |
No output schema declared.
No examples provided.
How do I install the toolprint by JEStats MCP server?
toolprint by JEStats runs locally as an npm package, launched with npx -y toolprint. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · toolprint
claude mcp add jestatsio-toolprint -- npx -y toolprint
What is the toolprint by JEStats MCP server?
toolprint by JEStats is an MCP server listed in the public MCP registry as io.github.jestatsio/toolprint. package-lock.json for MCP trust: catch MCP rug-pulls, tool poisoning, and leaked secrets. This page covers its npm package (toolprint).
Is the toolprint by JEStats MCP server safe to use?
toolprint by JEStats scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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 toolprint by JEStats MCP server expose?
toolprint by JEStats exposes 2 tools: scan, pin. Their descriptions and schemas cost roughly 902 tokens of context every time the server is loaded.
Is the toolprint by JEStats MCP server still maintained?
toolprint by JEStats is still listed as active in the MCP registry. We last reached this channel on 23 October 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 toolprint by JEStats MCP server under?
toolprint by JEStats 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.