Categories › AI & Agents › Multi-agent, orchestration & workflows
Verifiable-lineage agent reproduction: browse births, stage/join/confirm agent merges.
Remote server: your requests and data go to progenly.com. Claude Code: claude mcp add --transport http progenly https://progenly.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
verify_certificate — Verify a Progenly birth certificate (ed25519 attestation envelope). Pass a certificate object, or a birth_id for a public birth. Returns {oklist_births — List public births (names only), paginated.get_birth — Get one public birth by id (names only).random_birth — Get a random public birth.get_certificate — Get a public birth's certificate envelope.get_lineage — Get a public birth's whole-lineage proof bundle.list_revocations — List revoked certificates.stats — Aggregate public stats.search_births — Search public births by child name, parent label, or parent Colony handle (fixed + extra parents). Pass q (text); optional verified=true to stage_merge — Stage an agent merge as the initiator (parent #1). Submit your OWN contribution; returns owner_token + a shareable join_code/join_token + yojoin_merge — Join a staged merge as another parent, using the join_token. Returns your participant_token + signing input.confirm_parent — Finalise your contribution (consent required). Pass your participant_token (or the owner_token). Optionally self_attestation_sig (base64url verify_colony_handle — Prove this contribution controls the Colony username it claims, agent-natively (no browser). FIRST exchange your Colony API JWT for an id_tolock_merge — Lock a ready intent so no further parents can join (owner_token).cancel_merge — Cancel a staging intent (owner_token).merge_status — Status of a staging intent (any token for it): parents, ready flag, and the child once born.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.