Skip to main content
Glama
Anicodeth

package-verify-mcp

by Anicodeth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to package-verify-mcp

No user-submitted related servers found.

    Related Servers

    • pkgguard

      kiansaeidnia
      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.
      8 npm
      MIT

    • pkgproof

      jahija-okan
      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
      64 npm
      Apache 2.0

    • depscope-mcp

      cuttalo
      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.
      64 npm
      AGPL 3.0

    • pkgtruth

      hxckya
      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
      56 npm
      4
      MIT

    • pkgguard

      rxslice
      A
      license
      B
      quality
      A
      maintenance
      Pre-install gate for AI coding agents. Checks npm, PyPI and crates.io package names before an install runs and blocks names that do not exist, were registered after models invented them, or sit one keystroke from a popular package. CLI, GitHub Action and MCP server. Apache 2.0.
      1
      1
      Apache 2.0

    • npm-guardian

      Baneado98
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources