Skip to main content
Glama
mcp-tool-shop-org

mcp-shipcheck

by mcp-tool-shop-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-shipcheck

No user-submitted related servers found.

    Related Servers

    • license-guardian

      Baneado98
      -
      license
      Not graded
      quality
      B
      maintenance
      Audits npm dependencies for license compatibility, catching copyleft and source-available traps before shipping.
      -

    • 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

    • npm-supply-chain-audit-mcp

      tylerscomic-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables auditing package.json files for real npm supply-chain attack mechanisms — typosquatted dependency names, malicious preinstall/install/postinstall scripts that pipe downloads into a shell or decode base64 payloads, and unpinned versions — plus live npm registry lookups that flag nonexistent, brand-new, deprecated, or typosquatted packages. It exposes dedicated tools for full manifest audits and single-name typosquat checks.
      MIT

    • lockfile-guardian

      Baneado98
      A
      license
      Not graded
      quality
      D
      maintenance
      Audits your package-lock.json for supply-chain attacks before install. Cross-checks every resolved entry against the live npm registry to detect integrity mismatches, new install scripts, and other malicious signals.
      MIT

    • pkg-api-mcp

      Anicodeth
      A
      license
      A
      quality
      D
      maintenance
      Provides the real exported API surface and type signatures of any npm package, extracted from its published TypeScript declarations, enabling AI coding agents to use functions accurately and avoid inventing nonexistent APIs.
      3
      9 npm
      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.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: audit checks npm publish readiness, explainFailure decodes error codes, and packPreview shows file inclusions. An agent can easily distinguish between these three focused functions.

    Naming Consistency5/5

    All tools follow a perfect verb_noun pattern (audit, explainFailure, packPreview) with consistent dot notation (shipcheck.*) and snake_case for multi-word names. The naming is highly predictable and readable throughout.

    Tool Count5/5

    With 3 tools, this server is well-scoped for its purpose of npm package readiness checks. Each tool earns its place by covering distinct aspects (auditing, error explanation, and packing preview) without being overly sparse or bloated.

    Completeness4/5

    The toolset covers core npm package readiness workflows effectively: audit for checks, explainFailure for troubleshooting, and packPreview for validation. A minor gap exists in lacking a tool to directly fix issues (e.g., auto-correct or apply fixes), but agents can work around this using the explanations provided.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources