Penthera
NPM · PENTHERA
Offline, rule-based security checks for your repo, dependencies, AI agent config and local app.
Available components
Last scanned (22 hours ago)
Scores higher than 90% 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 Security100
- 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
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to danoszz/penthera). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 946 tokens (~157/item across 6 items; 6 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 Management40
- Stability observed for 12 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 140 → 157 ▼ functional
- Package version: 2.0.0 → 2.2.0 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 25 Oct 26 −10
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 1.00 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 1.9.0 → 2.0.0 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed npm/penthera@2.2.0
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 | danoszz/penthera |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/danoszz/penthera/.github/workflows/publish.yml@refs/tags/v2.2.0 |
| Rekor log index | 3634820362 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:53dd505a06d91697ff55d181abdf86a0bddc5e6b37f44845bfde9d67a3dfc9a6f1bd53d61608305424603dc8207379c85e6eb54eaffb9cb716feefb1b |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 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 →
audit_ai_tooling Audit AI agent config ~124
Audit the project's AI agent setup: skills, MCP servers, hooks, permissions, plugins and rule files, for hidden instructions, curl-pipe-shell, unpinned MCP packages, inline secrets and wildcard permissions. Grades A to F, or gives no grade when it finds no agent config. Offline, deterministic, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| max_findings | integer | – | How many findings to return, most severe first (default 50). |
| path | string | – | Project folder to scan, relative to the workspace root or absolute inside it. Default: the workspace root. |
No output schema declared.
No examples provided.
check_dependencies Check dependencies ~113
What each npm or Python dependency can do (install scripts, shell, network, eval, credential access), known-malicious packages and typosquats, read offline from the lockfile and installed tree. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| max_findings | integer | – | How many findings to return, most severe first (default 50). |
| path | string | – | Project folder to scan, relative to the workspace root or absolute inside it. Default: the workspace root. |
| prod | boolean | – | Skip dev dependencies (npm). |
No output schema declared.
No examples provided.
explain_finding Explain a finding ~105
Explain a finding's rule: what it checks, why it matters, how to fix it, effort, whether it is an owner action (rotate a key, change DNS), research references and OWASP MCP/Agentic ids. Pass the `rule` field of a finding as `id` (e.g. agents/mcp-unpinned, secrets, headers).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The finding's `rule`, e.g. agents/mcp-unpinned. |
No output schema declared.
No examples provided.
runtime_advisories Runtime advisories ~162
Is the PHP, nginx, Apache, Node.js, Python or OpenSSL an app runs affected by a published advisory, or past end of life? Give a project path (reads Dockerfiles, compose files and version pins) or the response headers you already have (Server, X-Powered-By). Offline.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | – | Response headers, e.g. {"server": "nginx/1.24.0", "x-powered-by": "PHP/8.1.2"}. |
| max_findings | integer | – | How many findings to return, most severe first (default 50). |
| path | string | – | Project folder to scan, relative to the workspace root or absolute inside it. Default: the workspace root. |
No output schema declared.
No examples provided.
scan_repo Scan a repository ~105
White-box scan of a local project folder: hardcoded secrets, code-execution sinks, API routes and trust boundaries, runtime versions with known advisories. Offline and read-only. Returns findings with evidence at file:line and confidence labels.
| Name | Type | Req | Description |
|---|---|---|---|
| max_findings | integer | – | How many findings to return, most severe first (default 50). |
| path | string | – | Project folder to scan, relative to the workspace root or absolute inside it. Default: the workspace root. |
No output schema declared.
No examples provided.
scan_url Scan a running app (passive) ~170
Passive black-box scan of a running web app the user is authorized to test: TLS, security headers, cookies, CORS, exposed files and docs, OpenAPI and auth checks. Sends no attack payloads: profile quick sends no login request, standard sends one POST /api/login with invalid credentials. Only loopback targets, or hosts the user listed with --allow-host when configuring this server, can be scanned, and a redirect off them is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| max_findings | integer | – | How many findings to return, most severe first (default 50). |
| profile | string | – | quick skips Retire.js and parameter discovery; standard is the full passive scan (default). |
| url | string | yes | http(s) URL of the app, e.g. http://localhost:3000 |
No output schema declared.
No examples provided.
How do I install the Penthera MCP server?
Penthera runs locally as an npm package, launched with npx -y penthera. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · penthera
claude mcp add danoszz-penthera -- npx -y penthera
What is the Penthera MCP server?
Penthera is an MCP server listed in the public MCP registry as io.github.danoszz/penthera. Offline, rule-based security checks for your repo, dependencies, AI agent config and local app. This page covers its npm package (penthera).
Is the Penthera MCP server safe to use?
Penthera scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Penthera MCP server expose?
Penthera exposes 6 tools: scan_repo, scan_url, check_dependencies, audit_ai_tooling, explain_finding, runtime_advisories. Their descriptions and schemas cost roughly 779 tokens of context every time the server is loaded.
Is the Penthera MCP server still maintained?
Penthera is still listed as active in the MCP registry. We last reached this channel on 4 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 Penthera MCP server under?
Penthera declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.