Codex Security Cloud MCP
Related Servers
Alternatives to Codex Security Cloud MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenancePrivate MCP server that enables a single GitHub identity to run Codex Security CLI scans on registered repositories, with OAuth authentication and a web-based cockpit UI.-
- AlicenseNot gradedqualityBmaintenanceStandalone MCP server that provides security scanning, project mapping, and vulnerability fix generation to AI coding assistants.27 npm2MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides coding agents with structured repository context, including graph-based navigation, dependency analysis, runtime flow tracing, and configuration surface across supported stacks.183 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that lets MCP clients inspect, create, update, and deploy ChatGPT Sites through a local Codex installation.1MIT

@repomend/mcpofficial
AlicenseNot gradedqualityDmaintenanceSecurity scanning MCP server that connects Claude to RepoMend findings, enabling vulnerability management and automated fix drafting.MIT- FlicenseNot gradedqualityBmaintenanceMCP server for AI DevTool workflow, exposing tools and resources for code review, repository chat, and repository operations.1-
TDQS
Scored across 7 tools
Each tool targets a distinct action (listing, fetching, closing, reopening, applying patches, requesting PRs, listing metadata) with no overlapping purposes, making agent selection unambiguous.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_findings, close_finding), providing predictable and readable naming.
Seven tools is well-scoped for a security findings server, covering essential operations without being too few (each tool has a clear role) or too many (no redundancy).
The tool set covers the full finding lifecycle: list, get, close, reopen, apply patch, and request site-side PR. Missing creation is natural (findings generated by system), and no dead ends exist.