Skip to main content
Glama
YoruichiYams

DevGuard-MCP

by YoruichiYams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to DevGuard-MCP

No user-submitted related servers found.

    Related Servers

    • opzyai

      thfothijn
      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

    • envguard

      1nc0gn30
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to scan and audit environment files for leaked secrets, sanitize them, encrypt/decrypt vaults, and run processes with zero-disk secret injection.
      MIT

    • RepoMind

      TaherFetoui
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants to inspect local and remote repositories through sandboxed tools that surface project overviews, structure, dependency audits, Git churn hotspots, and a heuristic health score. It also supports safe GitHub issue searching and creation with built-in duplicate preflight checks, while blocking sensitive files, binary content, and path traversal attacks.
      69 npm
      MIT

    • DevTwin MCP

      JaydeepDhamecha
      A
      license
      A
      quality
      B
      maintenance
      Provides AI coding agents with structured, evidence-based diagnostics about the local development environment, detecting tech stack, runtime mismatches, dependency state, services, ports, and Git status without exposing secrets or using network calls.
      10
      Apache 2.0
    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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: audit focuses on security risks, scan on reclaimable artifacts, preview/clean are paired, history and health are distinct. The only potential overlap is between audit_workspace_secrets and scan_workspace, as both may detect secrets, but their descriptions emphasize different objectives (security audit vs artifact discovery).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (audit, preview, get, clean, scan), with only minor variation like audit_workspace_secrets adding an extra noun. The style is uniform and predictable, making it easy to infer behavior from names.

    Tool Count5/5

    Six tools is well-scoped for a workspace hygiene server, covering scanning, auditing, previewing, cleaning, health metrics, and history. Each tool serves a distinct function without redundancy, and the count feels neither sparse nor bloated.

    Completeness4/5

    The surface covers the core lifecycle: scan (discover), audit (security), preview (simulate), clean (execute), plus health and history. Minor gaps exist such as no explicit tool for managing exclusion lists or restoring from recycle bin, but these are not critical for the primary workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources