Skip to main content
Glama

Related Servers

Alternatives to Redproof

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI editors such as Cursor, Claude Code, Windsurf and VS Code to scan a project for common AI-introduced security mistakes — leaked keys, open Supabase/Firebase data, missing auth, unverified Stripe webhooks, SQL injection and more — and return findings with exact fix instructions. It also provides a guided prompt that walks an agent through fixing critical issues one by one and verifying each fix by re-scanning, without ever editing files or rotating keys itself.
      2
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Predeploy security scanner for AI-generated code. 80+ vulnerability patterns across secrets, auth, injection, config, Supabase, and logging. Runs locally, code never leaves your machine. Optional x402 witnessed attestation.
      193 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to scan projects for security issues such as leaked API keys, missing Supabase RLS, open Firebase rules, unauthenticated routes, and hallucinated packages, then fix and verify the results.
      8
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to check whether an API key is safe to expose, audit Supabase Row Level Security, generate owner-based RLS policy templates, and run a builder-specific pre-launch security checklist. Runs locally over stdio with no network calls, telemetry, or file access.
      5
      MIT

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: one initiates a scan and returns a token, the other reads results using that token. There is no overlap in purpose and the descriptions make the sequence explicit.

    Naming Consistency5/5

    Both names follow a consistent snake_case verb_noun pattern (scan_github_repo, get_report) and are self-descriptive. No convention mixing.

    Tool Count3/5

    Two tools is thin for a service; the surface is essentially a single async operation split into start and poll. It is defensible for a narrow purpose but leaves little room for auxiliary operations.

    Completeness4/5

    The core lifecycle (start scan, fetch findings with fixes) is covered end to end. Minor gaps exist: no status/cancel, no listing or re-fetching of past scans, and polling relies on the caller retrying blindly.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues