PromptGuard
OCI · DOCKER.IO/ABHIJOYSARKAR/PROMPTGUARD-MCP-SERVER:1.1.2 · 2 COMPONENTS · SCANNED SEP 20
Scan prompts for injection attacks, redact PII, and audit LLM SDK usage from any MCP client
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.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 26 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability85
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 593 tokens (~98/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 Management90
- Stability observed for 27 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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
How do I install the PromptGuard MCP server?
PromptGuard runs locally as a container image, launched with docker run --rm -i docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2
claude mcp add co-promptguard-security -- docker run --rm -i docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2
{
"mcpServers": {
"co-promptguard-security": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
]
}
}
} {
"servers": {
"co-promptguard-security": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
]
}
}
} codex mcp add co-promptguard-security -- docker run --rm -i docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-promptguard-security": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
],
"enabled": true
}
}
} mcp_servers:
co-promptguard-security:
command: "docker"
args: ["run", "--rm", "-i", "docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"] {
"McpServers": {
"co-promptguard-security": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
]
}
}
} {
"mcpServers": {
"co-promptguard-security": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed oci/docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | Verification failed |
| Discovered via | OCI referrers API |
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 ~126
Authenticate with PromptGuard. When called without an api_key, opens the PromptGuard dashboard in the browser so the user can copy their API key -- then ask the user to provide it. When called with an api_key, validates and saves it. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | PromptGuard API key (starts with pg_live_). If omitted, opens the dashboard in the browser for the user to copy their key. |
No output schema declared.
No examples provided.
promptguard_logout ~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 ~94
Redact PII (emails, phone numbers, SSNs, credit cards, API keys, etc.) from text via the PromptGuard API. Returns sanitized text with entities replaced by placeholders. 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 |
No output schema declared.
No examples provided.
promptguard_scan_project ~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') |
No output schema declared.
No examples provided.
promptguard_scan_text ~99
Scan text for security threats (prompt injection, jailbreaks, PII leakage, toxic content) via the PromptGuard API. Returns a decision (allow/block), confidence score, threat type, and reason. 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 |
|---|---|---|---|
| text | string | yes | The text content to scan for security threats |
No output schema declared.
No examples provided.
promptguard_status ~66
Show current PromptGuard configuration and status for the project. Returns whether PromptGuard is initialized, API key type, proxy URL, configured providers, and CLI version. When to use: To verify PromptGuard is properly configured, check which providers are active, or confirm the installed CLI version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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 (docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2).
Is the PromptGuard MCP server safe to use?
PromptGuard scores 45 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 593 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.