Developer · Local MCP server
XploitScan
Security scanner for AI-generated code. 30 free rules; all 214 with a paid-plan API key.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.bgage72590/xploitscan-mcp- Version
- 1.6.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- bgage72590 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/bgage72590) · how
- Website
- xploitscan.com
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | xploitscan-mcp | 1.6.2 | stdio |
How to connect XploitScan
XploitScan runs locally from a Node.js package published to the npm registry: xploitscan-mcp version 1.6.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y xploitscan-mcp@1.6.2. It reads the environment variable XPLOITSCAN_API_KEY (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"xploitscan-mcp": {
"command": "npx",
"args": [
"-y",
"xploitscan-mcp@1.6.2"
],
"env": {
"XPLOITSCAN_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| xmp4 - Semantic code knowledge for your stackOSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+. | Remote · HTTPLive check: ✓ handshake |
| xOmniMarketSearch AI capabilities across AWS Marketplace and the Official MCP Registry. | Remote · HTTPLive check: ✓ handshake |
| xpay DevTools30+ dev tools. Context7, Code Runner, Python Execute, Code Sentinel, NPM Sentinel, PlantUML. | Remote · HTTP |
| Xplainable MCP ServerTrain, explain, optimise and deploy transparent glass-box ML models via workflow tools. | Remote · HTTPLive check: sign-in required |
| xytara MCP ExecutorPublic MCP server for summaries, DNS lookup, catalog, replies, and JSON checks. | Remote · HTTPLive check: ✓ handshake |
| YAACMessaging between concurrent AI coding sessions, across clients, over MCP. Zero infrastructure. | Local · stdio |
| Yaml Ai MCPAI-powered yaml ai MCP server for agents. Supports validate yaml, convert yaml json, lint yaml. By. | Local · stdio |
| Yandex Metrica MCPQuery Yandex Metrica analytics - reports, trends, metadata and raw log exports - via an AI agent. | Local · stdio |