PromptGuard
OCI · GHCR.IO/PROMPTGUARDHQ/PROMPTGUARD-MCP-SERVER · 3 COMPONENTS
Scan prompts for injection attacks, redact PII, and audit LLM SDK usage from any MCP client
Last scanned (11 hours ago)
Scores higher than 37% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 674 tokens (~112/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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
- Structured output schemas are declared (67% of tools); any adoption earns full credit.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 6 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +2
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 98 → 112 ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- MCP protocol: fail → pass ▲ functional
- First check of Tool coverage: 67 functional
- First check of Schema quality: unverified functional
- Package version: 1.1.3 → 1.2.0 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 32
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 5 Nov 2026 · Analysed oci/ghcr.io/promptguardhq/promptguard-mcp-server@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
promptguard_auth Connect PromptGuard ~122
Check whether PromptGuard is authenticated, and if not, open the PromptGuard dashboard so the user can create an API key. This tool never takes the key itself: the user saves it outside the chat, by running `promptguard login` in a terminal or by setting PROMPTGUARD_API_KEY in this MCP server's configuration. Never ask the user to paste an API key into the conversation. When to use: When any other promptguard tool reports that the user is not authenticated or not initialized, or when the user asks to log in to PromptGuard.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
promptguard_logout Log out of PromptGuard ~66
Log out of PromptGuard by removing the project-local configuration (.promptguard.json) and the globally stored API key (~/.promptguard/credentials.json). When to use: When the user wants to switch PromptGuard accounts, clear credentials, or ensure a clean state by removing existing authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
promptguard_redact Redact PII ~140
Redact PII (emails, phone numbers, SSNs, credit cards, API keys) from text. Returns sanitized text with each entity replaced by a labeled placeholder, e.g. [EMAIL_REDACTED], [PHONE_REDACTED], [SSN_REDACTED], and the PII types found. Never returns the original text. Each call counts as one Request on your PromptGuard plan. When to use: Before including user data in LLM prompts, when processing customer messages, or when building RAG pipelines that ingest documents containing personal information.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text content to redact PII from |
| Name | Type | Req | Description |
|---|---|---|---|
| piiFound | array | yes | – |
| redacted | string | yes | – |
No examples provided.
promptguard_scan_project Find unprotected LLM calls ~142
Performs static analysis on a project directory to detect unprotected LLM SDK usage (OpenAI, Anthropic, Cohere, Gemini, Bedrock, etc.). Returns detected providers, file locations (line/column), and instance count. When to use: During local development to find LLM calls that are not routed through PromptGuard, after generating new code that uses LLM SDKs, or when auditing an existing project for security coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Absolute path to the project directory to scan (defaults to current directory) |
| provider | string | – | Filter results to a specific provider (e.g. 'openai', 'anthropic') |
| Name | Type | Req | Description |
|---|---|---|---|
| files_scanned | integer | yes | – |
| providers | array | yes | – |
| summary | string | yes | – |
No examples provided.
promptguard_scan_text Scan text for threats ~129
Scan text for security threats including prompt injection, jailbreaks, PII leakage, and toxic content. Returns a decision (allow/block), confidence score, threat type, and reason. Each call counts as one Request on your PromptGuard plan. When to use: When reviewing user-facing prompts, testing LLM inputs for safety, or verifying that content is free of injection attacks before sending to an LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | Whether the text is a prompt sent to a model or a model's response |
| text | string | yes | The text content to scan for security threats |
| Name | Type | Req | Description |
|---|---|---|---|
| blocked | boolean | yes | – |
| confidence | number | yes | – |
| decision | string | yes | – |
| eventId | string|null | – | – |
| flagged | boolean | – | – |
| processingTimeMs | number|null | – | – |
| reason | string | yes | – |
| threatType | string|null | – | – |
No examples provided.
promptguard_status PromptGuard status ~75
Show whether PromptGuard is set up and signed in, with this server's version and the account or configuration details it knows (the hosted server reports your plan; the local CLI server reports its key type, proxy URL and providers). When to use: To verify PromptGuard is properly configured, or to confirm which version is running.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key_type | string | – | – |
| initialized | boolean | yes | – |
| message | string | – | – |
| providers | array | – | – |
| proxy_url | string | – | – |
| version | string | yes | – |
No examples provided.
How do I install the PromptGuard MCP server?
PromptGuard runs locally as a container image, launched with docker run --rm -i -e PROMPTGUARD_API_KEY ghcr.io/promptguardhq/promptguard-mcp-server:1.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/promptguardhq/promptguard-mcp-server
claude mcp add co-promptguard-security -- docker run --rm -i -e PROMPTGUARD_API_KEY ghcr.io/promptguardhq/promptguard-mcp-server:1.2.1
This image reads PROMPTGUARD_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the PromptGuard MCP server?
PromptGuard is an MCP server listed in the public MCP registry as co.promptguard/security. Scan prompts for injection attacks, redact PII, and audit LLM SDK usage from any MCP client. This page covers its container image (ghcr.io/promptguardhq/promptguard-mcp-server).
Is the PromptGuard MCP server safe to use?
PromptGuard scores 36 out of 100 on VerifyMCP. 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 PromptGuard MCP server expose?
PromptGuard exposes 6 tools: promptguard_auth, promptguard_logout, promptguard_scan_text, promptguard_scan_project, promptguard_redact, promptguard_status. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Is the PromptGuard MCP server still maintained?
PromptGuard 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.