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