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