Skip to main content
Glama
Sign In
closeread-verify

closeread-verify

by FreeGuy-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to closeread-verify

No user-submitted related servers found.

    Related Servers

    • license-sentinel

      wgd5678
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to audit Python and npm dependency licenses against your distribution context before shipping, returning CLEAN, REVIEW, or BLOCK verdicts with plain-language reasons and supporting notice generation.
      3
      1
      MIT

    • 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
      101 npm
      4
      MIT

    • pkgbouncer

      rayan1810
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to check package names and versions for allow/warn/deny verdicts, scan project lockfiles for known-malicious packages and critical advisories, and suggest safe versions across npm, PyPI, crates.io, and Go before manifests are edited.
      MIT

    • FreshStack MCP

      Jayesh01323
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to inspect project dependency versions, resolve version constraints, and audit Python code for deprecated or incompatible APIs using authoritative evidence and local AST analysis.
      3
      14 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool handles a distinct input: single file, multiple files, or a remote repository. The descriptions clearly differentiate their use cases without any overlap.

    Naming Consistency5/5

    All tools follow a consistent 'audit_' prefix with a clear noun suffix (_dependencies, _project, _repo), making the purpose immediately obvious.

    Tool Count5/5

    Three tools is perfectly scoped for the domain of dependency auditing, covering the primary input modes without unnecessary bloat.

    Completeness4/5

    The set covers the main workflows (single file, project, repo), but lacks a tool for auditing a directory without a known lockfile or for output customization, which are minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources