Umbra
Related Servers
Alternatives to Umbra
- AlicenseAqualityAmaintenanceMCP server for Cursor that scans codebases for security issues including hardcoded secrets, SAST, vulnerable dependencies, and IaC misconfigurations.7MIT
Related Servers

agentgraph-trustofficial
AlicenseAqualityCmaintenanceSecurity scanner and trust verification for AI agent tools. Scans GitHub repositories for vulnerabilities and returns signed trust attestations (Ed25519/JWS) with trust-tiered rate limiting recommendations.104MIT- AlicenseNot gradedqualityBmaintenanceLocal-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
- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.5 npm8MIT
- AlicenseAqualityDmaintenanceActs as a production-grade safety layer for AI-assisted coding, monitoring Git hygiene, scanning for security issues (PII, secrets, injection), and enabling semantic history search.9MIT
- AlicenseAqualityDmaintenanceAgent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.16 npm2MIT
- AlicenseBqualityDmaintenanceUniversal AI security layer for code scanning, PII detection, prompt injection defense, secret detection, dependency auditing, and audit logging.273Apache 2.0
TDQS
Scored across 3 tools
scan_repo and get_score both assess repository trust, but scan_repo provides a comprehensive report with findings while get_score is a fast static-only subset, making them distinguishable. guard_content is clearly distinct for write-time guarding.
All tool names follow the verb_noun snake_case pattern (scan_repo, get_score, guard_content), which is consistent and predictable.
Three tools is appropriate for the focused domain of repository trust scoring and content guarding; each tool has a clear purpose.
The set covers the main workflows: full scanning, quick scoring, and pre-write content guarding. Minor gaps exist, such as no explicit tool for retrieving historical reports or updating guard rules, but agents can work around these.