MCPSafe.io
RegistryThreatsMethodologyDocsPricingScanSign in
MCPSafe.io

Security checks for MCP servers — public packages and private repos, fast or deep.

Legal

Privacy PolicyCookie PolicyTerms of ServiceSecurity disclosure

Resources

State of MCP SecuritySupportSystem statusMade in Germany 🇩🇪

© 2026 MCPSafe. All rights reserved.

GDPR — Privacy Policy

Compare

Should I use A or B?

Paste two already-scanned packages to see a side-by-side security diff. Format: source/package or source/package@version — e.g. npm/@foo/bar, github/owner/repo, or npm/mcp-xmorf@1.0.2 to pin a version. Use two @version operands of the same package to diff two releases. Comparison reads from the cached scan; neither side is re-scanned. If a package isn’t cached yet, scan it first from the scan page.

B scores 19 points higher on MCPSafe's safety score.

Package A

server-filesystem

npm · 2026.1.14 · Last scan 7d ago

C

Score

68

Findings

9

Scans

0

Severity

critical0
high7
medium2
low0

Package B

server-memory

npm · 2026.1.26 · Last scan 11d ago

B

Score

87

Findings

2

Scans

0

Severity

critical0
high0
medium2
low0

Finding categories

Shared

  • server configuration

Only in A

  • prompt injection

Only in B

none

Our recommendationAI-assisted

Analyzing both scans…

Comparison is based on MCPSafe’s latest cached scan for each package. To re-scan a package on the newest commit, open it from the registry.