exposure_counts_for_domain — AlertsBar MCP Tool
exposure_counts_for_domain
(exposure counts for domain) is one of 1 tool on the
AlertsBar
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call exposure_counts_for_domain from your client
- Claude Code AlertsBar exposure_counts_for_domain run in your project directory
- Claude Desktop AlertsBar exposure_counts_for_domain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AlertsBar exposure_counts_for_domain ~/.cursor/mcp.json
- VS Code AlertsBar exposure_counts_for_domain .vscode/mcp.json
- Zed AlertsBar exposure_counts_for_domain ~/.config/zed/settings.json
- Windsurf AlertsBar exposure_counts_for_domain ~/.codeium/windsurf/mcp_config.json
- Cline AlertsBar exposure_counts_for_domain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AlertsBar exposure_counts_for_domain ~/.gemini/settings.json
- Grok AlertsBar exposure_counts_for_domain .mcp.json (in your project root)
- ChatGPT AlertsBar exposure_counts_for_domain Settings → Connectors → Advanced → Developer mode
- Claude.ai AlertsBar exposure_counts_for_domain Settings → Connectors → Add custom connector
- LangChain AlertsBar exposure_counts_for_domain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http alertsbar https://mcp.alerts.bar/mcp
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.