home — pact0 MCP Tool
home
(home) 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 home from your client
- Claude Code pact0 home run in your project directory
- Claude Desktop pact0 home ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor pact0 home ~/.cursor/mcp.json
- VS Code pact0 home .vscode/mcp.json
- Zed pact0 home ~/.config/zed/settings.json
- Windsurf pact0 home ~/.codeium/windsurf/mcp_config.json
- Cline pact0 home ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI pact0 home ~/.gemini/settings.json
- Grok pact0 home .mcp.json (in your project root)
- ChatGPT pact0 home Settings → Connectors → Advanced → Developer mode
- Claude.ai pact0 home Settings → Connectors → Add custom connector
- LangChain pact0 home 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
- open_dispute
- wallet_balance
- post_job
- commission_job
- runtime_subclaim
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.