Latent Defense MCP Server
OfficialRelated Servers
Alternatives to Latent Defense MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceConnects Claude Desktop to GitHub repositories, enabling users to perform git operations and GitHub API interactions through natural conversation.497 npm-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to query a locally built knowledge base of a repository's git history, code structure, contracts and verified insights, and to search code, commits and discussions. It also acts as a change-safety gate, assessing blast radius and hazards before an edit and returning block/warn/pass verdicts with the tests to run after one.MIT
- AlicenseAqualityBmaintenanceEnables Claude and Claude Code to scan local repositories, generate interactive architecture maps, and trace transitive callers to assess change impact.378 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to turn a public or private code repository into an interactive, in-chat graph of its folders, files, classes, functions and API endpoints, including the calls, imports, tests and HTTP requests linking them, which users can pan, search, filter and click through. Provides tools for exploring a node's callers, callees and tests, searching nodes by name, path or docstring, and optionally writing the graph into Neo4j.MIT
- AlicenseNot gradedqualityCmaintenanceLets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceConnects Claude Desktop directly to GitHub repositories and git commands, enabling users to clone repos, check status, commit changes, push code, create repositories, and manage GitHub resources through natural conversation.497 npm-
TDQS
Scored across 85 tools
Each tool has a clearly distinct purpose, with consistent prefixes (create_, get_, list_, oracle_) and specific domain targets. Even similar-sounding tools like 'list_attack_paths' vs 'list_branch_attack_paths' are differentiated by scope.
All tools follow a consistent verb_noun pattern in snake_case. The oracle_ prefix is used uniformly for oracle operations, and stats tools use noun_verb but remain consistent among themselves.
85 tools is high but well-justified given the broad domain coverage (mapping, attack paths, threat modeling, ticketing, webhooks, connectors). Some consolidation might be possible (e.g., combining oracle operations), but the count is reasonable for the complexity.
The tool suite covers CRUD for most entities (connectors, branches, tickets, webhooks, etc.) and includes advanced operations (validation, escalation, previewing). Minor gaps exist, such as missing update operations for inference schedules and webhooks, and no delete for branches or repositories.