CodeInspectus vs SecurityScan
CodeInspectus is an MCP server published by Synvoya. Marketplaces we read that list it: 1 (Official MCP Registry). SecurityScan is an MCP server published by apisecurityscan.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  CodeInspectus | |
|---|---|---|
| Official MCP Registry | Listed Version: 3.3.1 Downloads/month (npm): 942 Downloads/week (npm): 157 Forks (GitHub): 10 Stars (GitHub): 48 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | CodeInspectus | SecurityScan |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 | No figure on GitHub |
| Forks (GitHub) (differs) | 10 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (codeinspectus) | Remote server (apisecurityscan.net/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/synvoya/codeinspectus | github.com/securityscan-api/securityscan-api |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (20 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
CodeInspectus
Local-first MCP security scanner and CLI for AI-generated applications.
SecurityScan
Scan GitHub-hosted AI skills for vulnerabilities: prompt injection, malware, OWASP LLM Top 10.
How to run each
CodeInspectus As a local MCP server: npm package
claude mcp add --transport stdio codeinspectus -- npx -y codeinspectusSecurityScan As a remote MCP server
claude mcp add --transport http securityscan https://apisecurityscan.net/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SecurityScan has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: CodeInspectus · What it can do: SecurityScan · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.