Redproof
Related Servers
Alternatives to Redproof
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.2MIT
- AlicenseNot gradedqualityFmaintenancePredeploy 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 npmApache 2.0
- AlicenseAqualityBmaintenanceScan a deployed site for an exposed Supabase service_role key and audit Row Level Security from your AI coding agent.2460 npmMIT

shipsafe-mcpofficial
AlicenseAqualityCmaintenanceEnables 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.81MIT- AlicenseAqualityBmaintenance60-rule static security scanner and MCP skill poisoning auditor that detects leaked secrets, unguarded API routes, missing database RLS, and prompt injection in AI-generated codebases.231,171 npm45MIT
- AlicenseAqualityCmaintenanceEnables 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.5MIT
TDQS
Scored across 2 tools
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.
Both names follow a consistent snake_case verb_noun pattern (scan_github_repo, get_report) and are self-descriptive. No convention mixing.
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.
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.