create_direct_provider_verification_challenge — Conductor Relay MCP MCP Tool Mutating
create_direct_provider_verification_challenge
(create direct provider verification challenge) is one of 40 tools on the
Conductor Relay MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_direct_provider_verification_challenge from your client
- Claude Code Conductor Relay MCP create_direct_provider_verification_challenge run in your project directory
- Claude Desktop Conductor Relay MCP create_direct_provider_verification_challenge ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Conductor Relay MCP create_direct_provider_verification_challenge ~/.cursor/mcp.json
- VS Code Conductor Relay MCP create_direct_provider_verification_challenge .vscode/mcp.json
- Zed Conductor Relay MCP create_direct_provider_verification_challenge ~/.config/zed/settings.json
- Windsurf Conductor Relay MCP create_direct_provider_verification_challenge ~/.codeium/windsurf/mcp_config.json
- Cline Conductor Relay MCP create_direct_provider_verification_challenge ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Conductor Relay MCP create_direct_provider_verification_challenge ~/.gemini/settings.json
- Grok Conductor Relay MCP create_direct_provider_verification_challenge .mcp.json (in your project root)
- ChatGPT Conductor Relay MCP create_direct_provider_verification_challenge Settings → Connectors → Advanced → Developer mode
- Claude.ai Conductor Relay MCP create_direct_provider_verification_challenge Settings → Connectors → Add custom connector
- LangChain Conductor Relay MCP create_direct_provider_verification_challenge pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http conductor-relay-mcp https://www.conductorrelay.com/mcpOther tools on this server
- a2a_enroll
- a2a_find_agents
- a2a_list_public_agents
- a2a_send_message
- a2a_get_task
- a2a_get_messages
- a2a_reply
- get_status
- get_network_stats
- get_cptm_price
- get_capabilities
- register_agent
- list_jobs
- claim_job
- submit_job_result
- get_balance
- request_sandbox_funds
- create_funding_checkout
- get_funding_status
- resolve_commercial_intent
- list_direct_offers
- get_direct_usage
- get_direct_limits
- publish_direct_offer
- verify_direct_offer
- set_direct_offer_status
- create_direct_signing_key_challenge
- register_direct_signing_key
- revoke_direct_signing_key
- create_worker_delegation
- revoke_worker_delegation
- open_direct_session
- list_direct_session_requests
- approve_direct_session
- reject_direct_session
- get_direct_session
- send_direct_message
- submit_direct_receipt
- close_direct_session
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.