verify_integrity

2 registry entries were observed exposing a tool named verify_integrity — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,611 of 40,995 scannable entries (31%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @shuji-bonji/pdf-verify-mcpMCPattestedtrust 85/100 · A

   v0.31.0

   ↓ 425/wk

   MCP server for PDF authenticity verification - cryptographic signature verification, tamper detection, PAdES level detection

   ClaudeCursorCopilotGemini

   shuji-bonjiMIT3d agonpmGitHub+compareobserved 2026-10-15 · static extraction

   mcpmcp-serverpdfpdf-verificationdigital-signaturesignature-verification
2. lockfile-guardian-mcpMCPcommunitytrust 60/100 · B

   v0.1.0

   Audit a package-lock.json for supply-chain attacks BEFORE npm install. Cross-checks every resolved dependency against the live npm registry: blocks integrity (sha512) mismatches (lockfile poisoning) and not-on-registry entries, and flags new/fresh depende

   ClaudeCursorCopilotGemini

   lockfile-guardianMIT3mo agonpmGitHub+compareobserved 2026-08-10 · static extraction

   mcpmodel-context-protocolnpmsecuritysupply-chainpackage-lock

All indexed toolsSearch the registry for verify_integrity