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.

Security MCP

PYPI · SECURITY-MCP · SCANNED OCT 4

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

Available components

67 Trust /100
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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 1 of 21 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% 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 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 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.

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.

pypi · security-mcp

# add to Claude Code
claude mcp add pratham-jain33-security-mcp -- uvx security-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "pratham-jain33-security-mcp": {
      "command": "uvx",
      "args": [
        "security-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pratham-jain33-security-mcp": {
      "command": "uvx",
      "args": [
        "security-mcp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add pratham-jain33-security-mcp --command uvx --arg security-mcp
# ~/.hermes/config.yaml
mcp_servers:
  pratham-jain33-security-mcp:
    command: "uvx"
    args: ["security-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pratham-jain33-security-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "security-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add pratham-jain33-security-mcp -t stdio -c uvx -a security-mcp
// mcp.json
{
  "mcpServers": {
    "pratham-jain33-security-mcp": {
      "command": "uvx",
      "args": [
        "security-mcp"
      ]
    }
  }
}
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.

  • 1 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Sept 26 52

    First indexed and scored.

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 Oct 2026 · Analysed pypi/security-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 pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 21 packages
Packages resolved 21
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~412 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
audit_site ~136

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.

NameTypeReqDescription
domainstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

check_cve ~139

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.

NameTypeReqDescription
cve_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

lookup_attack ~137

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.

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

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.