XploitScan
NPM · XPLOITSCAN-MCP · SCANNED SEP 26
Security scanner for AI-generated code. Scan, explain rules, and grade before you ship.
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 Security98
- 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
- 40 of 138 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 286 tokens (~95/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 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
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 supported MCP spec version (2025-11-25); the latest is 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.
How do I install the XploitScan MCP server?
XploitScan runs locally as an npm package, launched with npx -y xploitscan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · xploitscan-mcp
claude mcp add bgage72590-xploitscan-mcp -- npx -y xploitscan-mcp
{
"mcpServers": {
"bgage72590-xploitscan-mcp": {
"command": "npx",
"args": [
"-y",
"xploitscan-mcp"
]
}
}
} {
"servers": {
"bgage72590-xploitscan-mcp": {
"command": "npx",
"args": [
"-y",
"xploitscan-mcp"
]
}
}
} codex mcp add bgage72590-xploitscan-mcp -- npx -y xploitscan-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bgage72590-xploitscan-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"xploitscan-mcp"
],
"enabled": true
}
}
} openclaw mcp add bgage72590-xploitscan-mcp --command npx --arg -y --arg xploitscan-mcp
mcp_servers:
bgage72590-xploitscan-mcp:
command: "npx"
args: ["-y", "xploitscan-mcp"] {
"McpServers": {
"bgage72590-xploitscan-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"xploitscan-mcp"
]
}
}
} assistant mcp add bgage72590-xploitscan-mcp -t stdio -c npx -a -y xploitscan-mcp
{
"mcpServers": {
"bgage72590-xploitscan-mcp": {
"command": "npx",
"args": [
"-y",
"xploitscan-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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Sept 26 51
First indexed and scored.
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 26 Sept 2026 · Analysed npm/xploitscan-mcp@1.5.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 138 packages
| Packages resolved | 138 |
|---|---|
| Deprecated | 1 |
| Stale | 39 |
| 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 →
explain_rule ~104
Look up the description, severity, OWASP category, CWE, and remediation guidance for a specific XploitScan rule by its rule ID (e.g. 'VC005' for unprotected Stripe webhooks, 'VC006' for SQL injection). Use this when a user asks what a specific finding means or how to fix it.
| Name | Type | Req | Description |
|---|---|---|---|
| ruleId | string | yes | The XploitScan rule ID, e.g. 'VC005', 'VC006', 'VC132'. |
No output schema declared.
No examples provided.
grade_code ~77
Scan code AND compute a security grade (A+ through F) with a score (0-100) and summary. Use this as a single-call 'is this code safe to ship' check — typically after generating a feature or before committing.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | The files to grade. Same shape as scan_code's files parameter. |
No output schema declared.
No examples provided.
scan_code ~105
Scan source code for security vulnerabilities using XploitScan's 214 rules tuned for AI-generated code. Returns a list of findings with rule ID, severity, file, line, description, and fix suggestion. Use this when the user asks you to check code for security issues, or before you write code to a file.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | The files to scan. Pass an array of { path, content } objects — typically the files you just wrote or about to write. |
No output schema declared.
No examples provided.
What is the XploitScan MCP server?
XploitScan is an MCP server listed in the public MCP registry as io.github.bgage72590/xploitscan-mcp. Security scanner for AI-generated code. Scan, explain rules, and grade before you ship. This page covers its npm package (xploitscan-mcp).
Is the XploitScan MCP server safe to use?
XploitScan scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 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 XploitScan MCP server expose?
XploitScan exposes 3 tools: scan_code, explain_rule, grade_code. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Is the XploitScan MCP server still maintained?
XploitScan is still listed as active in the MCP registry. We last reached this channel on 26 September 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 XploitScan MCP server under?
XploitScan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.