Skip to main content
Glama
shipcheck-mcp

shipcheck-mcp

by TateLyman

Related Servers

Alternatives to shipcheck-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI coding agents to perform zero-execution, AST-based static analysis of JavaScript/TypeScript codebases, including symbol lookup, dependency tracing, change-impact analysis, dead-code detection, and risk assessment.
      8
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables an AI agent to discover JavaScript in a web app, scan it for exposed secrets and known vulnerable libraries, and review verified findings through structured MCP tools and a local dashboard.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Local-first, zero-egress security scanner for AI-generated / "vibe-coded" JS/TS. Bundles Opengrep, Gitleaks & Trivy behind one CWE-keyed schema and adds AI-code-specific checks (client-side secret exposure, Supabase RLS, prompt-injection & LLM-output XSS sinks). No account, no telemetry.
      10
      358 npm
      51
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Security checks for code an AI agent is about to trust. vetcode_guard checks a command before it installs packages or adds an MCP server: made-up names, look-alikes, malware advisories, brand-new releases, and the archive read without running it. vetcode_scan reads a folder for malware, supply-chain attacks, attacks on agents, leaked secrets and risky config. Local, zero dependencies.
      4
      2
      MIT

    TDQS

    A3.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no chance of confusion between tools. The single tool has a clear and distinct purpose.

    Naming Consistency5/5

    With only one tool, there are no naming inconsistencies. The name 'scan_repository' follows a clear snake_case convention.

    Tool Count3/5

    A single tool feels thin for most purposes, though for a very specialized server like 'shipcheck' it might be acceptable. It borders on too minimal.

    Completeness3/5

    The server only offers one operation (scanning), which may be insufficient for a full workflow. Missing potential tools like listing results or configuration, but the core task is covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues