conformance_check — Live-Payload Conformance Probes MCP Tool
conformance_check
(conformance check) is one of 1 tool on the
Live-Payload Conformance Probes
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call conformance_check from your client
- Claude Code Live-Payload Conformance Probes conformance_check run in your project directory
- Claude Desktop Live-Payload Conformance Probes conformance_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Live-Payload Conformance Probes conformance_check ~/.cursor/mcp.json
- VS Code Live-Payload Conformance Probes conformance_check .vscode/mcp.json
- Zed Live-Payload Conformance Probes conformance_check ~/.config/zed/settings.json
- Windsurf Live-Payload Conformance Probes conformance_check ~/.codeium/windsurf/mcp_config.json
- Cline Live-Payload Conformance Probes conformance_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Live-Payload Conformance Probes conformance_check ~/.gemini/settings.json
- Grok Live-Payload Conformance Probes conformance_check .mcp.json (in your project root)
- ChatGPT Live-Payload Conformance Probes conformance_check Settings → Connectors → Advanced → Developer mode
- Claude.ai Live-Payload Conformance Probes conformance_check Settings → Connectors → Add custom connector
- LangChain Live-Payload Conformance Probes conformance_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http live-payload-conformance-probes https://textforagents.com/products/live-payload-conformance-probes/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 20 October 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.