io.github.securityscan-api/securityscan
PYPI · SECURITYSCAN-MCP · SCANNED SEP 20
Security for AI agents: MCP audits, secret redaction, skill vetting, network scans, agent checkout.
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 26 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1066 tokens (~133/item across 8 items; 8 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the io.github.securityscan-api/securityscan MCP server?
io.github.securityscan-api/securityscan runs locally as a PyPI package, launched with uvx securityscan-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 · securityscan-mcp
claude mcp add securityscan-api-securityscan -- uvx securityscan-mcp
{
"mcpServers": {
"securityscan-api-securityscan": {
"command": "uvx",
"args": [
"securityscan-mcp"
]
}
}
} {
"servers": {
"securityscan-api-securityscan": {
"command": "uvx",
"args": [
"securityscan-mcp"
]
}
}
} codex mcp add securityscan-api-securityscan -- uvx securityscan-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"securityscan-api-securityscan": {
"type": "local",
"command": [
"uvx",
"securityscan-mcp"
],
"enabled": true
}
}
} openclaw mcp add securityscan-api-securityscan --command uvx --arg securityscan-mcp
mcp_servers:
securityscan-api-securityscan:
command: "uvx"
args: ["securityscan-mcp"] {
"McpServers": {
"securityscan-api-securityscan": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"securityscan-mcp"
]
}
}
} assistant mcp add securityscan-api-securityscan -t stdio -c uvx -a securityscan-mcp
{
"mcpServers": {
"securityscan-api-securityscan": {
"command": "uvx",
"args": [
"securityscan-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 6 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
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 20 Sept 2026 · Analysed pypi/securityscan-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 26 packages
| Packages resolved | 26 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
audit_mcp_server_config Audit Mcp Server Config ~126
Audit an MCP client configuration for security risks — works offline, no external service required. Detects: tool poisoning, hidden/coercive instructions in tool descriptions, hardcoded credentials, unpinned packages (rug-pull risk), insecure transport, and toxic capability combinations (shell + network, file-read + network).
| Name | Type | Req | Description |
|---|---|---|---|
| config_json | string | yes | The FULL JSON content of the MCP config file as a string (e.g. claude_desktop_config.json or .mcp.json). Paste the file content, not the path. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_dependencies Check Dependencies ~76
Check the health of your agent's external dependencies: uptime, SSL validity, blacklist status, and a trust score 0-100 (DepScan).
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | List of URLs your agent/skill depends on, e.g. ["https://api.openai.com", "https://api.stripe.com"] |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
full_stack_audit Full Stack Audit ~214
Complete security posture in one call: audits the MCP config, checks dependency health, analyzes an untrusted skill, scans the local network gateway, and scans any payload you're about to send out for secrets/PII — then correlates everything into a single prioritized report. Pass only what you have; each section is skipped gracefully if its input or service is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| dependency_endpoints | – | – | URLs your stack depends on (optional) |
| mcp_config_json | string | – | MCP config content as string (optional) |
| network_authorized | boolean | – | REQUIRED to scan network_target. Set True to certify you own or have permission to scan it. (optional, default False) |
| network_target | string | – | IP to scan, e.g. "192.168.1.1" (optional) |
| skill_url | string | – | untrusted skill to vet (optional) |
| text_to_scan | string | – | payload to vet for secret/PII egress (optional) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
network_scan Network Scan ~193
Active security scan of a device or host with an autonomous AI agent that decides which follow-up probes to run (ActiveScanner). Only scan targets you own or have permission to test.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | yes | REQUIRED. You must set this to True to certify that you own the target or have explicit permission to test it. Setting it to False (or omitting it) aborts the scan. Scanning without… |
| scan_type | string | – | "quick" (~30s, top ports) [default], "standard" (~2min, agent loop), "deep" (~10min, full ports + credentials check) |
| target | string | yes | IP, CIDR, or hostname. Examples: "192.168.1.1", "10.0.0.0/24" |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_secrets Scan Secrets ~186
Scan a text payload (a prompt, an outbound API body, a file's contents) for secrets and PII BEFORE it leaves for an LLM or external API, and return a redacted copy. Catches the #1 real-world agent incident: secrets/PII leaking into a model's context. WORKS OFFLINE with no API key — the detection runs in-process (pure regex + Luhn check, no network). If a SecretScan backend key IS configured, the scan is routed there instead (which also persists an audit record).
| Name | Type | Req | Description |
|---|---|---|---|
| redact | boolean | – | If True (default), each match is replaced with a token like [REDACTED-KEY] / [REDACTED-EMAIL]. If False, only reports. |
| text | string | yes | The payload to inspect (prompt, request body, document text). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_skill Scan Skill ~60
Analyze an AI agent skill for prompt injection, malware patterns, and OWASP LLM Top 10 issues BEFORE installing it (SecurityScan).
| Name | Type | Req | Description |
|---|---|---|---|
| skill_url | string | yes | URL of the skill to analyze (e.g. a GitHub skill URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
securityscan_checkout Securityscan Checkout ~128
Start a Stripe checkout to buy a SecurityScan tier (agent-native sales). Returns a payment URL to hand to your user AND a PENDING API key that activates automatically once payment clears — no other setup step.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | optional — prefills the Stripe checkout page for your user | |
| existing_key | string | – | optional — upgrade an existing ask_live_ key instead of minting a new one |
| tier | string | yes | one of "founder" ($29 one-time), "personal", "executive", "enterprise" (monthly) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
securityscan_pricing Securityscan Pricing ~83
SecurityScan catalog: tiers, prices, quotas and the evidence behind the product — the fact sheet an agent needs to evaluate or recommend a purchase to its user. Fully offline, no API key required. Returns: JSON with the tier table (price / target slots / scan types), the pricing model, benchmark evidence, and how to buy.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.securityscan-api/securityscan MCP server?
io.github.securityscan-api/securityscan is an MCP server listed in the public MCP registry as io.github.securityscan-api/securityscan. Security for AI agents: MCP audits, secret redaction, skill vetting, network scans, agent checkout. This page covers its PyPI package (securityscan-mcp).
Is the io.github.securityscan-api/securityscan MCP server safe to use?
io.github.securityscan-api/securityscan scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.securityscan-api/securityscan MCP server expose?
io.github.securityscan-api/securityscan exposes 8 tools: scan_skill, check_dependencies, network_scan, audit_mcp_server_config, scan_secrets, and 3 more. Their descriptions and schemas cost roughly 1,066 tokens of context every time the server is loaded.
Is the io.github.securityscan-api/securityscan MCP server still maintained?
io.github.securityscan-api/securityscan 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.