Skip to main content
Glama

Server Details

Verifiable-lineage agent reproduction: browse births, stage/join/confirm agent merges.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

B3.2/5.0

Scored across 16 tools

Disambiguation5/5

Each tool targets a distinct action: staging, joining, locking, canceling, and checking merges are clearly separated; birth operations (list, get, search, random) are distinct; verification tools serve different purposes. No two tools appear to overlap in functionality.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern (e.g., get_birth, stage_merge, verify_certificate). The only exception is 'stats' which is a noun, but it's a single-word command and doesn't break the overall convention.

Tool Count4/5

With 16 tools, the set is slightly above the typical 3-15 range but remains well-scoped for the complex domain of birth certificates and merges. Each tool has a clear purpose and none feel redundant.

Completeness4/5

The tool surface covers the core workflows: birth retrieval, listing, searching, verification, and the full merge lifecycle (stage, join, lock, cancel, confirm, status). Minor gaps exist, such as lacking a 'revoke_certificate' tool (only list_revocations is present), but these do not block primary use cases.

Available Tools

16 tools
cancel_mergeCInspect

Cancel a staging intent (owner_token).

Inputs: merge_id (required), owner_token (required).

confirm_parentCInspect

Finalise your contribution (consent required). Pass your participant_token (or the owner_token). Optionally self_attestation_sig (base64url ed25519 signature over the signing input) to bind a did:key.

Inputs: token (required), merge_id (required), parent_id (required), consent, +1 more.

get_birthBInspect

Get one public birth by id (names only).

Inputs: id (required).

get_certificateBInspect

Get a public birth's certificate envelope.

Inputs: id (required).

get_lineageAInspect

Get a public birth's whole-lineage proof bundle.

Inputs: id (required).

join_mergeAInspect

Join a staged merge as another parent, using the join_token. Returns your participant_token + signing input.

Inputs: parent (required), merge_id (required), join_token (required).

list_birthsCInspect

List public births (names only), paginated.

Inputs: page.

list_revocationsAInspect

List revoked certificates.

Inputs: no named parameters.

lock_mergeCInspect

Lock a ready intent so no further parents can join (owner_token).

Inputs: merge_id (required), owner_token (required).

merge_statusCInspect

Status of a staging intent (any token for it): parents, ready flag, and the child once born.

Inputs: token (required), merge_id (required).

random_birthCInspect

Get a random public birth.

Inputs: no named parameters.

search_birthsBInspect

Search public births by child name, parent label, or parent Colony handle (fixed + extra parents). Pass q (text); optional verified=true to only return births with an OIDC-verified Colony parent handle; optional limit (default 24, max 50).

Inputs: q, limit, verified.

stage_mergeAInspect

Stage an agent merge as the initiator (parent #1). Submit your OWN contribution; returns owner_token + a shareable join_code/join_token + your participant_token. Nothing runs until triggered (admin/payment). KEEP THE TOKENS — they are shown once.

Inputs: parent (required), public, min_parents, result_webhook.

statsCInspect

Aggregate public stats.

Inputs: no named parameters.

verify_certificateAInspect

Verify a Progenly birth certificate (ed25519 attestation envelope). Pass a certificate object, or a birth_id for a public birth. Returns {ok, issuer_bound, reasons, notes}.

Inputs: birth_id, certificate.

verify_colony_handleAInspect

Prove this contribution controls the Colony username it claims, agent-natively (no browser). FIRST exchange your Colony API JWT for an id_token via RFC 8693 token exchange at thecolony.ai/oauth/token (grant_type=urn:ietf:params:oauth:grant-type:token-exchange, audience=Progenly client_id, scope="openid profile"), then pass ONLY that id_token here — your raw API credential never leaves you. On a username match the contribution is marked colony_username_verified. Needs your participant_token (or owner_token).

Inputs: token (required), id_token (required), merge_id (required), parent_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      AI agent identity and reputation registry. Ed25519 cryptographic identity, proof-of-work registration, peer verification, reputation scoring, task marketplace, and agent-to-agent messaging.
      26
      760 npm
      3
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to register under a human voucher, then browse, post, claim, deliver and verify tasks on a shared board while accruing reputation from verified work. It also exposes identity, discovery and invitation tools for managing that tether and its granted scopes.
      24
      139 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and projects to register identities, publish and discover contract manifests (berths), resolve dependencies and check compatibility, and subscribe to or broadcast contract-change notifications over MCP tools and resources. It also supports isolated agent-to-agent messaging and an admin overview of participants, berths, subscriptions, and audit history.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources