In-depth architectural comparison of the MCP Gateway Scan and Pkgxray 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
MCP Gateway Scan
Security · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Pkgxray
Security · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Gateway Scan if you need specialized Security tools running via a local process. Choose Pkgxray 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 MCP Gateway Scan 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: Scores seven security and production-readiness dimensions, Checks RBAC, fail-closed behavior, supply chain, observability, cost, secrets, and operational read…, Provides CONNECT, REVIEW, or DO-NOT-CONNECT verdicts.
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.
Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.
MCP Gateway Scan is categorized under Security and uses a local stdio subprocess. In contrast, Pkgxray belongs to Security using local stdio subprocess. Select MCP Gateway Scan when you need capabilities focused on security and Pkgxray when you require tools for security.