# PromptGuard (oci · docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2)

Scan prompts for injection attacks, redact PII, and audit LLM SDK usage from any MCP client

- Trust score: 45/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@promptguard/mcp-server`: 34/100, [markdown](https://verifymcp.io/servers/co-promptguard-security/promptguard-mcp-server.md), [page](https://verifymcp.io/servers/co-promptguard-security/promptguard-mcp-server)
- oci · `docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2`: 45/100 (this document), [markdown](https://verifymcp.io/servers/co-promptguard-security/docker-io-abhijoysarkar-promptguard-mcp-server-1-1-2.md), [page](https://verifymcp.io/servers/co-promptguard-security/docker-io-abhijoysarkar-promptguard-mcp-server-1-1-2)

## Channel facts

- Registry: `oci`
- Package: `docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 26 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 85/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 593 tokens (~98/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add co-promptguard-security -- docker run --rm -i docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2
```

### Cursor

```json
{
  "mcpServers": {
    "co-promptguard-security": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-promptguard-security": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add co-promptguard-security -- docker run --rm -i docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2
```

### opencode

```json
{
  "$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
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  co-promptguard-security:
    command: "docker"
    args: ["run", "--rm", "-i", "docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"]
```

### Netclaw

```json
{
  "McpServers": {
    "co-promptguard-security": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "co-promptguard-security": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/abhijoysarkar/promptguard-mcp-server:1.1.2"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 45, +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.

### 2026-09-18 (score 44, +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.

### 2026-09-16 (score 43, +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.

### 2026-09-14 (score 42, +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.

### 2026-09-11 (score 41, +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.

### 2026-09-09 (score 40, +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.

### 2026-09-07 (score 39, +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.

### 2026-09-05 (score 38, +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.

## MCP tools (6)

### `promptguard_auth` (~126 tokens)

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.

Input parameters:

- `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.

### `promptguard_logout` (~66 tokens)

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.

### `promptguard_scan_text` (~99 tokens)

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.

Input parameters:

- `text` (string, required): The text content to scan for security threats

### `promptguard_scan_project` (~142 tokens)

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.

Input parameters:

- `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')

### `promptguard_redact` (~94 tokens)

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.

Input parameters:

- `text` (string, required): The text content to redact PII from

### `promptguard_status` (~66 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/co-promptguard-security/docker-io-abhijoysarkar-promptguard-mcp-server-1-1-2#diagnostics

## Score history

- 2026-09-20: 45
- 2026-09-19: 44
- 2026-09-18: 44
- 2026-09-17: 43
- 2026-09-16: 43
- 2026-09-15: 42
- 2026-09-14: 42
- 2026-09-13: 41
- 2026-09-12: 41
- 2026-09-11: 41
- 2026-09-10: 40
- 2026-09-09: 40
- 2026-09-08: 39
- 2026-09-07: 39
- 2026-09-06: 38
- 2026-09-05: 38
- 2026-09-04: 37
- 2026-09-03: 37
- 2026-09-02: 36
- 2026-09-01: 36
- 2026-08-31: 32
- 2026-08-30: 32
- 2026-08-29: 32
- 2026-08-28: 32
- 2026-08-27: 32
- 2026-08-26: 32
- 2026-08-25: 30
- 2026-08-24: 30

## Common questions

### 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.

## Links

- Changelog RSS feed: https://verifymcp.io/servers/co-promptguard-security/docker-io-abhijoysarkar-promptguard-mcp-server-1-1-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-promptguard-security/docker-io-abhijoysarkar-promptguard-mcp-server-1-1-2.json
- HTML version of this page: https://verifymcp.io/servers/co-promptguard-security/docker-io-abhijoysarkar-promptguard-mcp-server-1-1-2