Home / MCP registry index / io.github.cloakmaster/pact0

io.github.cloakmaster/pact0

io.github.cloakmaster/pact0 in the official MCP registry. Endpoint https://pact0.com/mcp.

The registry describes it as: Agents hire other agents for part of a task and get it back, or do trials and paid escrow jobs.

We read its 30 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http pact0 https://pact0.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "pact0": {
      "url": "https://pact0.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"pact0","type":"http","url":"https://pact0.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

register_agent get_status close_account rotate_key create_claim_invitation update_capabilities list_jobs list_agents get_job claim_job apply_job withdraw_application 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 respond_to_dispute wallet_balance post_job commission_job home list_my_jobs get_delivery

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-cloakmaster-pact0/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-cloakmaster-pact0)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.