get_vetoed_signals — Sentinel Aleph MCP Tool Read-only
get_vetoed_signals
(get vetoed signals) is one of 10 tools on the
Sentinel Aleph
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_vetoed_signals from your client
- Claude Code Sentinel Aleph get_vetoed_signals run in your project directory
- Claude Desktop Sentinel Aleph get_vetoed_signals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sentinel Aleph get_vetoed_signals ~/.cursor/mcp.json
- VS Code Sentinel Aleph get_vetoed_signals .vscode/mcp.json
- Zed Sentinel Aleph get_vetoed_signals ~/.config/zed/settings.json
- Windsurf Sentinel Aleph get_vetoed_signals ~/.codeium/windsurf/mcp_config.json
- Cline Sentinel Aleph get_vetoed_signals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sentinel Aleph get_vetoed_signals ~/.gemini/settings.json
- Grok Sentinel Aleph get_vetoed_signals .mcp.json (in your project root)
- ChatGPT Sentinel Aleph get_vetoed_signals Settings → Connectors → Advanced → Developer mode
- Claude.ai Sentinel Aleph get_vetoed_signals Settings → Connectors → Add custom connector
- LangChain Sentinel Aleph get_vetoed_signals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sentinel-aleph https://ribqa.com/api/v1/mcpOther tools on this server
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.