Security Audit — coderegistry MCP Resource
Security Audit
is one of 34 resources on the
coderegistry
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Security Audit from your client
- Claude Code coderegistry Resource/Security Audit run in your project directory
- Claude Desktop coderegistry Resource/Security Audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor coderegistry Resource/Security Audit ~/.cursor/mcp.json
- VS Code coderegistry Resource/Security Audit .vscode/mcp.json
- Zed coderegistry Resource/Security Audit ~/.config/zed/settings.json
- Windsurf coderegistry Resource/Security Audit ~/.codeium/windsurf/mcp_config.json
- Cline coderegistry Resource/Security Audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI coderegistry Resource/Security Audit ~/.gemini/settings.json
- Grok coderegistry Resource/Security Audit .mcp.json (in your project root)
- ChatGPT coderegistry Resource/Security Audit Settings → Connectors → Advanced → Developer mode
- Claude.ai coderegistry Resource/Security Audit Settings → Connectors → Add custom connector
- LangChain coderegistry Resource/Security Audit pip install langchain-mcp-adapters
Other resources on this server
- Docs Index
- AGENTS.md
- The Code Registry MCP Server
- Changelog
- LICENSE
- MCP API Reference
- Architecture - Source Code Types
- Authentication
- Facet Glossary
- Getting Started
- Response Schemas
- Troubleshooting
- GitHub Integration Workflow
- Local Repo Analysis Workflow
- Multi-Project Setup
- M&A Due Diligence with Claude
- Portfolio Monitoring
- Tech Debt Analysis
- Analyze code on every PR
- GitLab CI example
- jenkins-pipeline
- Claude API Integration
- Example of using Code Registry MCP via Claude API
- typescript-example
- Claude Desktop Setup
- config
- Cline (VS Code) Setup
- Cursor Setup
- Custom MCP Clients
- nodejs-client
- python-client
- api-responses
- mcp-tools
coderegistry also offers 4 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.