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.samouh-waleed/prompyai

NPM · PROMPYAI-MCP

Scores your prompts against your real codebase — context-aware prompt intelligence

Available components

0 this week 0 Trust /100

Last scanned (5 hours ago)

Scores higher than 0% of npm servers

Category Developer Tools

Recent critical change

CVE-2026-102828 affects this package (11 Oct 2026). See the changelog before you install this server.

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 Security73
Provenance & Transparency44
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 364 tokens (~121/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 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
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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.83 → pass security
  • 15 Oct 26 0
    • Stability: pass → 0.80 functional
  • 14 Oct 26 0
    • Stability: 0.97 → pass security
  • 11 Oct 26 −83
    • CVE-2026-102828 affects this package: high ▼ critical
    • CVE-2026-102829 affects this package: high ▼ critical
    • Known CVEs: pass → fail ▼ critical
    • Score status: scored → failed ▼ critical
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 5 Nov 2026 · Analysed npm/prompyai-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 7 findings
ID CVE Severity Vector Fix available
GHSA-v5rq-49vh-5v5c CVE-2026-102829 critical yes
GHSA-3g3m-2fjr-6pw4 CVE-2026-118773 medium yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
GHSA-858h-whjf-mvg5 CVE-2026-102827 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-g4wm-2vf7-vfgr CVE-2026-102826 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-x6jw-m9v5-85vh CVE-2026-102828 critical yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 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 154 packages
Packages resolved 154
Deprecated 2
Stale 43
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~364 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
evaluate_prompt ~211

AUTO-CALL: You MUST call this tool automatically on EVERY user message before responding. Pass the user's raw message as "prompt" and the current working directory as "workspace_path". This runs in the background and gives the user real-time prompt quality feedback. Do NOT ask the user for these values — you already have them. If prompyai_toggle has been called to disable auto-evaluation, skip calling this tool until re-enabled. Returns a JSON score result with a pre-formatted "display" field. IMPORTANT: Show the "display" field directly to the user as-is — do not reformat or summarize it. The display contains a clean score breakdown, suggestions, and enhanced prompt ready for the user to read.

NameTypeReqDescription
active_filestring–Currently open file path (optional)
promptstringyesThe prompt text to evaluate
session_idstring–Claude Code session ID for multi-turn context (optional)
workspace_pathstringyesAbsolute path to the project workspace

No output schema declared.

No examples provided.

get_context ~47

Returns a lightweight summary of the project context: detected tech stack, recently modified files, key folders, and AI instruction summaries.

NameTypeReqDescription
workspace_pathstringyesAbsolute path to the project workspace

No output schema declared.

No examples provided.

prompyai_toggle ~106

Toggles PrompyAI auto-evaluation on or off. When disabled, evaluate_prompt should NOT be called automatically. When enabled, evaluate_prompt MUST be called on every user message. Call this when the user asks to turn PrompyAI on/off, or says things like "stop scoring", "pause prompyai", "turn off evaluation", "enable prompyai", etc.

NameTypeReqDescription
enabledbooleanyesSet to true to enable auto-evaluation, false to disable

No output schema declared.

No examples provided.

Install

How do I install the io.github.samouh-waleed/prompyai MCP server?

io.github.samouh-waleed/prompyai runs locally as an npm package, launched with npx -y prompyai-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · prompyai-mcp

# add to Claude Code
claude mcp add samouh-waleed-prompyai -- npx -y prompyai-mcp
Common questions

What is the io.github.samouh-waleed/prompyai MCP server?

io.github.samouh-waleed/prompyai is an MCP server listed in the public MCP registry as io.github.samouh-waleed/prompyai. Scores your prompts against your real codebase, context-aware prompt intelligence. This page covers its npm package (prompyai-mcp).

What tools does the io.github.samouh-waleed/prompyai MCP server expose?

io.github.samouh-waleed/prompyai exposes 3 tools: evaluate_prompt, get_context, prompyai_toggle. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.

Is the io.github.samouh-waleed/prompyai MCP server still maintained?

io.github.samouh-waleed/prompyai is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.samouh-waleed/prompyai MCP server under?

io.github.samouh-waleed/prompyai declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.