io.github.joeyough/mcpcheck vs io.github.vpatser1/mcp-server-security-scanner
io.github.joeyough/mcpcheck is an MCP server published by joeyough. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vpatser1/mcp-server-security-scanner is an MCP server published by vpatser1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |  io.github.joeyough/mcpcheck | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 1.1.4 Downloads/month (npm): 131 Downloads/week (npm): 51 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 | io.github.joeyough/mcpcheck | io.github.vpatser1/mcp-server-security-scanner |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcpcheck.netlify.app/mcp) | On your machine (mcp-server-security-scanner) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/joeyough/mcpcheck | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 h ago | no remote endpoint we check |
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
io.github.joeyough/mcpcheck
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
io.github.vpatser1/mcp-server-security-scanner
Scan MCP configs for 30+ CVEs, prompt injection, tool poisoning; validate OAuth configs
How to run each
io.github.joeyough/mcpcheck As a remote MCP server
claude mcp add --transport http mcpcheck https://mcpcheck.netlify.app/mcpio.github.vpatser1/mcp-server-security-scanner As a local MCP server: npm package
claude mcp add --env "LICENSE_KEY=<YOUR_LICENSE_KEY>" --transport stdio mcp-server-security-scanner -- npx -y mcp-server-security-scannerRequires: LICENSE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.joeyough/mcpcheck 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
The marketplaces of io.github.joeyough/mcpcheck publish no settings it asks for, so we do not compare settings.
What it can do: io.github.joeyough/mcpcheck · What it can do: io.github.vpatser1/mcp-server-security-scanner · 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.