Promptheus
PYPI · PROMPTHEUS
AI-powered prompt refinement with adaptive questioning and multi-provider support (6+ LLM backends)
Available components
Last scanned (15 hours ago)
Scores higher than 3% of PyPI servers
Category AI and Machine Learning
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 Security32
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects filelock 3.32.7, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs poetry.core.masonry.api at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 68 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 300 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- CVE-2026-112938 affects this package: high ▼ security
- CVE-2026-112915 affects this package: high ▼ security
- CVE-2026-112936 affects this package: high ▼ security
- CVE-2026-112912 affects this package: high ▼ security
- CVE-2026-112911 affects this package: high ▼ security
- CVE-2026-112910 affects this package: high ▼ security
- CVE-2026-112935 affects this package: high ▼ security
- CVE-2026-112909 affects this package: high ▼ security
- CVE-2026-112939 affects this package: high ▼ security
- CVE-2026-112908 affects this package: high ▼ security
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 −3
- CVE-2026-112940 affects this package: high ▼ security
- CVE-2026-112907 affects this package: high ▼ security
- CVE-2026-112913 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects filelock 3.32.7, a direct dependency. A fixed version is available. security
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Dependency health: partial → 0.98 functional
- 15 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Dependency health: 0.98 → partial functional
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 pypi/promptheus@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | poetry.core.masonry.api |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 27 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-567q-5qvw-pf92 | CVE-2026-112907 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-6627-m3xw-93mp | CVE-2026-112908 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-69hj-f68j-2879 | CVE-2026-112909 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-8mx5-7m5m-r77g | CVE-2026-112910 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-9c4x-gm8v-wgc4 | CVE-2026-112911 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-9j6q-wvj5-jgjg | CVE-2026-112912 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-9vhv-jxww-xfm5 | CVE-2026-112913 | low | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-cwqr-hh33-gh44 | CVE-2026-112915 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-fq56-3cx3-fjxp | CVE-2026-112935 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-j8f7-rjxc-mr56 | CVE-2026-112936 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-m462-7rxw-wvpg | CVE-2026-112938 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H | yes |
| GHSA-rfpc-qcw5-3pc4 | CVE-2026-112939 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-v4x8-3wr5-3wq8 | CVE-2026-112940 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-2c2j-9gv5-cj73 | CVE-2025-54121 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-7f5h-v6xp-fcq8 | CVE-2025-62727 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-82w8-qh3p-5jfq | CVE-2026-54283 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-86qp-5c8j-p5mr | CVE-2026-48710 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-jp82-jpqv-5vv3 | CVE-2026-54282 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-wqp7-x3pw-xc5r | CVE-2026-48818 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-x746-7m8f-x49c | CVE-2026-48817 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-161 | CVE-2026-48710 | none | yes | |
| PYSEC-2026-1941 | CVE-2025-54121 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| PYSEC-2026-1942 | CVE-2025-62727 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-2280 | CVE-2026-48817 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-2281 | CVE-2026-48818 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-248 | CVE-2026-54282 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-249 | CVE-2026-54283 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 68 packages
| Packages resolved | 68 |
|---|---|
| Stale | 4 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the Promptheus MCP server?
Promptheus runs locally as a PyPI package, launched with uvx promptheus. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · promptheus
claude mcp add abhichandra21-promptheus -- uvx promptheus
What is the Promptheus MCP server?
Promptheus is an MCP server listed in the public MCP registry as io.github.abhichandra21/promptheus. AI-powered prompt refinement with adaptive questioning and multi-provider support (6+ LLM backends). This page covers its PyPI package (promptheus).
Is the Promptheus MCP server safe to use?
Promptheus scores 13 out of 100 on VerifyMCP. We recorded 27 known advisories against it as of 4 November 2026. 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.
Is the Promptheus MCP server still maintained?
Promptheus 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 Promptheus MCP server under?
Promptheus declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.