get-security-issues — coderegistry MCP Tool Read-only
get-security-issues
(get security issues) is one of 23 tools on the
coderegistry
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get-security-issues from your client
- Claude Code coderegistry get-security-issues run in your project directory
- Claude Desktop coderegistry get-security-issues ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor coderegistry get-security-issues ~/.cursor/mcp.json
- VS Code coderegistry get-security-issues .vscode/mcp.json
- Zed coderegistry get-security-issues ~/.config/zed/settings.json
- Windsurf coderegistry get-security-issues ~/.codeium/windsurf/mcp_config.json
- Cline coderegistry get-security-issues ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI coderegistry get-security-issues ~/.gemini/settings.json
- Grok coderegistry get-security-issues .mcp.json (in your project root)
- ChatGPT coderegistry get-security-issues Settings → Connectors → Advanced → Developer mode
- Claude.ai coderegistry get-security-issues Settings → Connectors → Add custom connector
- LangChain coderegistry get-security-issues pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http coderegistry https://integrator.app.thecoderegistry.com/api/ai/router
Other tools on this server
- create_account
- list_projects
- get_project
- create_project
- delete_project
- list_vaults
- get_vault
- create-code-vault
- reanalyze-code-vault
- delete-code-vault
- get-code-vault-summary
- get-code-vault-results
- get-code-vault-reports
- get_account
- delete_account
- rotate_api_key
- get-code-smells
- get-git-history
- get-contributors
- get-components
- get-code-iq-automated-queries
- get-the-code-score
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.