AppLedger
OfficialRelated Servers
Alternatives to AppLedger
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceSecurity scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.61314Apache 2.0- AlicenseNot gradedqualityDmaintenanceLocal-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
- AlicenseAqualityAmaintenanceLocal-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.10211 npm50Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAutomatically detects security vulnerabilities in AI-generated code, scanning for hardcoded secrets, injection flaws, XSS, weak cryptography, authentication issues, path traversal, and vulnerable dependencies across JavaScript, Python, Java, and Go.14 npm2MIT
- 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.94 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceAI-powered security scanner for Python projects and GitHub repositories. Detects vulnerabilities, secrets, and provides AI risk assessment.11MIT
TDQS
Scored across 5 tools
Each tool targets a distinct action: preview, scan, retrieve fix request, connect dashboard, and check service status. The only real overlap is between preview_upload and check_app, which itself returns an upload_preview on first run; the descriptions explain the difference, but an agent may still wonder which to call first.
All names are snake_case and mostly follow a verb_noun pattern (preview_upload, get_fix_prompt, connect_dashboard, check_app). scanner_status is noun-first rather than a verb, a minor deviation but still clear.
Five tools is well-scoped for a security-check service: scan, preview, retrieve fix guidance, connect, and status. Nothing feels redundant or missing from the count perspective.
The scan lifecycle is covered: preview what's sent, run the check, get the fix prompt, verify the scanner, and connect to the dashboard. Minor gaps exist — no way to disconnect/revoke a saved key or list prior check results beyond the on-disk files.