Security for AI agents: MCP audits, secret redaction, skill vetting, network scans, agent checkout.
MCPpedia last refreshed this data
io.github.securityscan-api/securityscan is an MCP server that security for AI agents: MCP audits, secret redaction, skill vetting, network scans, agent checkout. Its tool list has not been published yet over stdio, requires no API key, and scores 54/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"securityscan": {
"env": {
"DEPSCAN_API_KEY": "dsk_live_...",
"SECRETSCAN_API_KEY": "ssc_...",
"SECURITYSCAN_API_KEY": "ss_live_...",
"ACTIVESCANNER_API_KEY": "ask_live_..."
},
"args": [
"-m",
"stack.unified_mcp_server"
],
"command": "python"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Security for AI agents: MCP audits, secret redaction, skill vetting, network scans, agent checkout.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
uvx 'securityscan-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked securityscan-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / ecommerce
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
MCP Security Weekly
Get CVE alerts and security updates for io.github.securityscan-api/securityscan and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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).
pip install securityscan-mcp
That's it — the package is on PyPI.
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.
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: ..."
| 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 checko |