Pkgxray vs MCP Gateway Scan — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Pkgxray vs MCP Gateway Scan
In-depth architectural comparison of the Pkgxray and MCP Gateway Scan MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Pkgxray
Security · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
MCP Gateway Scan
Security · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Pkgxray if you need specialized Security tools running via a local process. Choose MCP Gateway Scan if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Pkgxray when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Static quarantine scans that normally do not execute package code, SAFE, REVIEW, and BLOCK verdicts with exit codes, File-level cited evidence for detected findings.
Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.
Read-only static scanner for MCP / agent-gateway production-readiness. The scangateway tool scores a repo across 7 security dimensions (RBAC, fail-closed, supply chain, observability, cost, secrets, prod-readiness). Never executes code or prints secret values.
Pkgxray is categorized under Security and uses a local stdio subprocess. In contrast, MCP Gateway Scan belongs to Security using local stdio subprocess. Select Pkgxray when you need capabilities focused on security and MCP Gateway Scan when you require tools for security.