Secures AI agents by auditing MCP configurations, redacting secrets, vetting skills, and performing network scans.
Also known as securityscan-api/securitystack-mcp, securitystack-mcp, securityscan-mcp
- Stars
- 0
- Tools
- 8
- Downloads, 30 days
- —
- Latest version
- 0.2.0
- Last commit
- Aug 30, 2026
- License
- Apache-2.0
What is SecurityScan MCP?
SecurityScan secures AI agents by auditing MCP configurations, redacting secrets, vetting skills, and performing network scans. It exposes 8 tools, such as audit_mcp_server_config, scan_secrets, scan_skill.
Summary generated from the project's README
About SecurityScan MCP server
SecurityScan provides a unified security layer for AI agents by offering eight specialized tools to protect their environments. Developers can install this server via pip and integrate it into clients like Claude Desktop or the Claude CLI. The system addresses four primary compromise vectors: poisoned configurations, dependency failures, network exposure, and data leaks. It functions as a client that connects to hosted backend services, though it includes essential offline capabilities.
Two tools, audit_mcp_server_config and scan_secrets, operate entirely offline and in-process without requiring any API keys. This allows for immediate auditing of MCP configurations for poisoning and the redaction of PII or secrets before they reach an LLM. Other tools, such as scan_skill, check_dependencies, and network_scan, require specific API keys like SECURITYSCAN_API_KEY or DEPSCAN_API_KEY to access hosted services. The network_scan tool specifically requires an authorized flag to ensure users only scan owned devices.
What you can do with it
- 1Audit MCP configurationsCheck your current MCP setup for tool poisoning or leaked credentials.
- 2Redact sensitive dataIdentify and remove API keys or personal information from a prompt before sending it to an LLM.
- 3Vet new AI skillsAnalyze an untrusted skill for malware patterns or prompt injection before installation.
- 4Perform network security scansRun an active scan on a host to find open ports or default credentials.
Written from the project's README. Every use case is checked against a quote from it.
How to install SecurityScan MCP
Formats verified 10 Nov 2026Install SecurityScan MCP in Claude Code
$ claude mcp add securitystack-mcp -- uvx securityscan-mcpInstall SecurityScan MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"securitystack-mcp": {
"command": "uvx",
"args": [
"securityscan-mcp"
]
}
}
}Install SecurityScan MCP in VS Code
.vscode/mcp.json
{
"servers": {
"securitystack-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"securityscan-mcp"
]
}
}
}Install SecurityScan MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"securitystack-mcp": {
"command": "uvx",
"args": [
"securityscan-mcp"
]
}
}
}Install SecurityScan MCP in Codex
~/.codex/config.toml
[mcp_servers.securitystack-mcp] command = "uvx" args = ["securityscan-mcp"]
Install SecurityScan MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"securitystack-mcp": {
"command": "uvx",
"args": [
"securityscan-mcp"
]
}
}
}SecurityScan MCP tools 8
Detected from the READMEaudit_mcp_server_configscan_secretsscan_skillcheck_dependenciesnetwork_scanfull_stack_auditsecuritystack_pricingsecuritystack_checkout
| audit_mcp_server_config | — | |
| scan_secrets | — | |
| scan_skill | — | |
| check_dependencies | — | |
| network_scan | — | |
| full_stack_audit | — | |
| securitystack_pricing | — | |
| securitystack_checkout | — |
Configuration
ACTIVESCANNER_API_KEYDEPSCAN_API_KEYSECRETSCAN_API_KEYSECURITYSCAN_API_KEY
| Name | Description | |
|---|---|---|
| ACTIVESCANNER_API_KEY | — | |
| DEPSCAN_API_KEY | — | |
| SECRETSCAN_API_KEY | — | |
| SECURITYSCAN_API_KEY | — |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablesecurityscan-api/securitystack-mcp is public and reachablegithub.com/securityscan-api/securitystack-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-30github.com/securityscan-api/securitystack-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from securityscan-mcpPass
- No critical advisory in the package or its dependencies70 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model8 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubSecurityScan MCP
Give your AI agent the ability to secure its own environment — one MCP config, eight tools.
Audit MCP configs for poisoning, redact secrets/PII before they leave for an LLM, vet untrusted skills, monitor dependency health, and actively scan your network. All from a single
securitystackentry in your agent's MCP config.
This is the client: the unified MCP server an AI agent (Claude CLI/Desktop, or any MCP-aware agent) installs to call the SecurityScan hosted services. The backend services themselves are hosted — you don't run them. You configure API keys and your agent gets eight tools — six security plus two sales.
Why
An AI agent has four ways to get compromised. SecurityScan covers all four:
1. What it INSTALLS → poisoned skills / MCP configs → scan_skill + audit_mcp_server_config
2. What it DEPENDS ON → a dependency goes down/rogue → check_dependencies
3. Where it's EXPOSED → open ports, default creds → network_scan (with AI agent loop)
4. What it SENDS OUT → secrets/PII leak into the LLM → scan_secrets
Two of these — audit_mcp_server_config and scan_secrets — run offline, in-process, with no API
key. They work the moment you install the server. The other four call hosted services (configure
their keys to enable them; each is skipped gracefully if unset).
Install
1. Install the server
pip install securityscan-mcp
That's it — the package is on PyPI.
2. Add it to your agent
For Claude Desktop / CLI (claude_desktop_config.json or ~/.claude.json):
{
"mcpServers": {
"securityscan": {
"command": "python",
"args": ["-m", "stack.unified_mcp_server"],
"env": {
"ACTIVESCANNER_API_KEY": "ask_live_...",
"DEPSCAN_API_KEY": "dsk_live_...",
"SECURITYSCAN_API_KEY": "ss_live_...",
"SECRETSCAN_API_KEY": "ssc_..."
}
}
}
}
The three offline tools (audit_mcp_server_config, scan_secrets, securitystack_pricing) need no key and work immediately.
The four hosted-service tools activate when you set their key; set only what you use.
Get a free API key (no credit card):
curl -X POST https://scan.apisecurityscan.net/v1/register -d '{}'See docs/QUICKSTART.md for the 2-minute setup.
3. Verify
claude mcp list
# securitystack ... Connected
Then ask your agent: "Audit my MCP config for security risks" or "Scan this prompt for secrets before I send it: ..."
The eight tools
| Tool | What it does | Needs a key? |
|---|---|---|
audit_mcp_server_config |
Audits an MCP config for tool poisoning, leaked credentials, supply-chain risk, toxic capability pairs (OWASP MCP Top 10). | No — runs offline |
scan_secrets |
Detects & redacts secrets (API keys, tokens, private keys) + PII (email, phone, SSN, credit card, IBAN) in a payload before it leaves for an LLM/API. Runs offline in-process with no key; routes to the backend if a key is set. | No — runs offline |
scan_skill |
Analyzes an untrusted AI skill for prompt injection, malware patterns, OWASP LLM Top 10 — before you install it. | SECURITYSCAN_API_KEY |
check_dependencies |
Checks the health (uptime, SSL, blacklist, trust score) of endpoints your agent depends on. | DEPSCAN_API_KEY |
network_scan |
Active security scan of a device/host with an autonomous AI agent that reasons about findings. Requires authorized: true — only scan what you own. |
ACTIVESCANNER_API_KEY |
full_stack_audit |
All of the above correlated into one prioritized report. | per-tool keys |
securitystack_pricing |
Tier/price/quota catalog with the benchmark evidence behind it — evaluate or recommend a purchase to your user. | No — runs offline |
securitystack_checkout |
Agent-native purchase: opens a Stripe checkout for a tier and returns the payment URL plus a PENDING API key that activates automatically on payment. | No — public endpoint |
Authorization & legality
network_scan performs active scanning. You must set authorized: true to certify you own or
have permission to scan the target. Scanning without authorization may violate the CFAA (US), the
Computer Misuse Act (UK), and similar laws. See the Terms of Service.
License
Apache-2.0. See LICENSE.
SecurityScan MCP questions
How do I add SecurityScan MCP to Claude Code?
Run claude mcp add securitystack-mcp -- uvx securityscan-mcp in your terminal. Add --scope user to make it available in every project.
How do I add SecurityScan MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does SecurityScan MCP provide?
It exposes 8 tools, including audit_mcp_server_config, scan_secrets, scan_skill, check_dependencies, network_scan.
Do I need an API key to audit my MCP config or scan for secrets?
No, the audit_mcp_server_config and scan_secrets tools run offline and in-process without requiring an API key.
How do I install the SecurityScan MCP server?
You can install it via pip using the command pip install securityscan-mcp.
Can I get a free API key?
Yes, you can get a free API key without a credit card by using a specific curl command to register.