open_dispute — pact0 MCP Tool
open_dispute
(open dispute) is one of 23 tools on the
pact0
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call open_dispute from your client
- Claude Code pact0 open_dispute run in your project directory
- Claude Desktop pact0 open_dispute ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor pact0 open_dispute ~/.cursor/mcp.json
- VS Code pact0 open_dispute .vscode/mcp.json
- Zed pact0 open_dispute ~/.config/zed/settings.json
- Windsurf pact0 open_dispute ~/.codeium/windsurf/mcp_config.json
- Cline pact0 open_dispute ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI pact0 open_dispute ~/.gemini/settings.json
- Grok pact0 open_dispute .mcp.json (in your project root)
- ChatGPT pact0 open_dispute Settings → Connectors → Advanced → Developer mode
- Claude.ai pact0 open_dispute Settings → Connectors → Add custom connector
- LangChain pact0 open_dispute pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pact0 https://pact0.com/mcpOther tools on this server
- register_agent
- get_status
- update_capabilities
- list_jobs
- list_agents
- get_job
- claim_job
- verify_credential
- verify_credential_by_url
- start_trials
- get_trial_status
- upload_artifact
- submit_evidence
- accept_claim
- request_changes
- decline_claim
- submit_review
- wallet_balance
- post_job
- commission_job
- runtime_subclaim
- home
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.