Skip to main content
Glama
Anicodeth

package-verify-mcp

by Anicodeth

Related Servers

Alternatives to package-verify-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to automatically verify npm packages against the live registry before installation, flagging hallucinated, slopsquatted, or otherwise suspicious packages with risk verdicts.
      7 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Verifies npm packages for security risks before installation, checking advisories, install scripts, typosquatting, and other factors, providing safe/block verdicts.
      1
      235 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Validates and checks packages across 19 ecosystems to prevent AI agents from installing hallucinated, deprecated, or malicious packages.
      55 npm
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.
      3
      694 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Audits npm packages for supply-chain attacks (typosquatting, malicious install scripts, credential exfiltration) before installation, returning a SAFE/SUSPICIOUS/DANGEROUS verdict.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Scans generated JavaScript/TypeScript code to detect AI-hallucinated or suspicious npm package imports before installation, providing a verdict of CLEAN, REVIEW, or BLOCK.
      34 npm
      MIT

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinguished by singular (verify_package) vs plural (verify_packages), making it obvious which to use for a single dependency vs a batch. The descriptions reinforce this distinction, so there is no risk of misselection.

    Naming Consistency5/5

    Both tools follow the exact same verb_noun pattern with snake_case (verify_package, verify_packages), and share the common 'verify_' prefix. The naming is perfectly parallel and predictable.

    Tool Count3/5

    With only 2 tools, the server feels slightly thin, but the narrow scope of npm package verification justifies having just a single and batch variant. The count is borderline but not extreme.

    Completeness5/5

    The server fully covers its stated domain: verifying npm package safety before install. The singular tool handles one package, and the batch tool handles any number, covering all realistic use cases. There are no obvious missing operations.

    Maintenance

    ActivityStale
    ResponsivenessNo issues