Breach402 Trust Contract — Breach402 Owner Protection MCP Resource
Breach402 Trust Contract
is one of 5 resources on the
Breach402 Owner Protection
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Breach402 Trust Contract from your client
- Claude Code Breach402 Owner Protection Resource/Breach402 Trust Contract run in your project directory
- Claude Desktop Breach402 Owner Protection Resource/Breach402 Trust Contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Breach402 Owner Protection Resource/Breach402 Trust Contract ~/.cursor/mcp.json
- VS Code Breach402 Owner Protection Resource/Breach402 Trust Contract .vscode/mcp.json
- Zed Breach402 Owner Protection Resource/Breach402 Trust Contract ~/.config/zed/settings.json
- Windsurf Breach402 Owner Protection Resource/Breach402 Trust Contract ~/.codeium/windsurf/mcp_config.json
- Cline Breach402 Owner Protection Resource/Breach402 Trust Contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Breach402 Owner Protection Resource/Breach402 Trust Contract ~/.gemini/settings.json
- Grok Breach402 Owner Protection Resource/Breach402 Trust Contract .mcp.json (in your project root)
- ChatGPT Breach402 Owner Protection Resource/Breach402 Trust Contract Settings → Connectors → Advanced → Developer mode
- Claude.ai Breach402 Owner Protection Resource/Breach402 Trust Contract Settings → Connectors → Add custom connector
- LangChain Breach402 Owner Protection Resource/Breach402 Trust Contract pip install langchain-mcp-adapters
Other resources on this server
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.