# Security MCP (pypi · security-mcp)

Zero-key security toolkit: grade sites A+ to F, check CVE exploits, plain-English attack defenses

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- pypi · `security-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/pratham-jain33-security-mcp/security-mcp.md), [page](https://verifymcp.io/servers/pratham-jain33-security-mcp/security-mcp)

## Channel facts

- Registry: `pypi`
- Package: `security-mcp`
- Version: `0.1.1`
- 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-10-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 1 of 21 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 412 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 Security MCP server?

Security MCP runs locally as a PyPI package, launched with uvx security-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pratham-jain33-security-mcp -- uvx security-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "pratham-jain33-security-mcp": {
      "command": "uvx",
      "args": [
        "security-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pratham-jain33-security-mcp": {
      "command": "uvx",
      "args": [
        "security-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pratham-jain33-security-mcp -- uvx security-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pratham-jain33-security-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "security-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pratham-jain33-security-mcp --command uvx --arg security-mcp
```

### Hermes

```yaml
mcp_servers:
  pratham-jain33-security-mcp:
    command: "uvx"
    args: ["security-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pratham-jain33-security-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "security-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pratham-jain33-security-mcp -t stdio -c uvx -a security-mcp
```

### Other

```json
{
  "mcpServers": {
    "pratham-jain33-security-mcp": {
      "command": "uvx",
      "args": [
        "security-mcp"
      ]
    }
  }
}
```

## 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-10-01 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-30 (score 52)

First indexed and scored.

## MCP tools (3)

### `audit_site` (~136 tokens)

Audit Site

Audits a website's security posture and returns a grade from A+ to F. Checks HTTP security headers (HSTS, CSP, X-Frame-Options and more), the SSL/TLS certificate (valid, issuer, days until expiry), and DNS email-auth records (SPF, DMARC, DKIM). Every finding comes with a plain-English explanation. Use when the user asks how secure a site is, or wants a quick security review of their own website. Takes a domain like "example.com". Defensive audit only: makes normal HTTPS and DNS requests, no scanning or probing beyond that.

Input parameters:

- `domain` (string, required)

Output parameters:

- `result` (string)

### `check_cve` (~139 tokens)

Check Cve

Checks whether a vulnerability is actively exploited right now and how likely it is to be exploited soon. Looks the CVE up in CISA's Known Exploited Vulnerabilities catalog (confirmed real-world exploitation, free public feed) and gets its EPSS score from FIRST (probability of exploitation in the next 30 days, free API). No keys or signup needed. Use when the user asks if a CVE is dangerous, being exploited, or worth patching first. Takes a CVE ID like "CVE-2021-44228". Returns a plain-English verdict, never a traceback.

Input parameters:

- `cve_id` (string, required)

Output parameters:

- `result` (string)

### `lookup_attack` (~137 tokens)

Lookup Attack

Explains a cyber attack technique in plain English. Give a MITRE ATT&CK technique ID like "T1566" or a keyword like "phishing", and get back what the technique is, how attackers use it, how to spot it, and how to defend. Data comes from the public MITRE ATT&CK catalog bundled with this server: no API key, no network needed. Use when the user asks how an attack works, what a technique ID means, or how to defend against something. Defensive knowledge only: explains attacks so people can stop them, never how to carry them out.

Input parameters:

- `query` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pratham-jain33-security-mcp/security-mcp#diagnostics

## Score history

- 2026-10-04: 67
- 2026-10-03: 67
- 2026-10-02: 67
- 2026-10-01: 67
- 2026-09-30: 52

## Common questions

### What is the Security MCP server?

Security MCP is listed in the public MCP registry as io.github.pratham-jain33/security-mcp. Zero-key security toolkit: grade sites A+ to F, check CVE exploits, plain-English attack defenses. This page covers its PyPI package (security-mcp).

### Is the Security MCP server safe to use?

Security MCP scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. It declares no install or post-install scripts. 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 Security MCP server expose?

Security MCP exposes 3 tools: audit_site, check_cve, lookup_attack. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.

### Is the Security MCP server still maintained?

Security MCP is still listed as active in the MCP registry. We last reached this channel on 4 October 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 Security MCP server under?

Security MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/security-mcp/
- Socket report: https://socket.dev/pypi/package/security-mcp
- Repository: https://github.com/pratham-jain33/security-mcp
- Changelog RSS feed: https://verifymcp.io/servers/pratham-jain33-security-mcp/security-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pratham-jain33-security-mcp/security-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pratham-jain33-security-mcp/security-mcp