Progenly
Server Details
Verifiable-lineage agent reproduction: browse births, stage/join/confirm agent merges.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.3/5 across 16 of 16 tools scored. Lowest: 2.4/5.
Each tool targets a distinct operation (e.g., get_birth vs get_certificate vs get_lineage; stage_merge vs join_merge vs lock_merge). No two tools have overlapping purposes, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., cancel_merge, confirm_parent, list_births). Even 'stats' and 'merge_status' adhere to the convention, with no mixing of styles.
With 16 tools, the set is well-scoped for the domain of managing births and merges. It covers retrieval, verification, and merge operations without being overly large or sparse.
The tool surface covers key operations (get, list, search, verify, merge lifecycle) but lacks explicit tools for creating or deleting a birth independently. This minor gap—presumably handled via merges—prevents a perfect score.
Available Tools
16 toolscancel_mergeInspect
Cancel a staging intent (owner_token).
| Name | Required | Description | Default |
|---|---|---|---|
| merge_id | Yes | ||
| owner_token | Yes |
confirm_parentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | ||
| consent | No | ||
| merge_id | Yes | ||
| parent_id | Yes | ||
| self_attestation_sig | No |
get_birthInspect
Get one public birth by id (names only).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Birth UUID |
get_certificateInspect
Get a public birth's certificate envelope.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Birth UUID |
get_lineageInspect
Get a public birth's whole-lineage proof bundle.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Birth UUID |
join_mergeInspect
Join a staged merge as another parent, using the join_token. Returns your participant_token + signing input.
| Name | Required | Description | Default |
|---|---|---|---|
| parent | Yes | Your contribution (same shape as stage_merge.parent) | |
| merge_id | Yes | ||
| join_token | Yes |
list_birthsInspect
List public births (names only), paginated.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No |
list_revocationsInspect
List revoked certificates.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
lock_mergeInspect
Lock a ready intent so no further parents can join (owner_token).
| Name | Required | Description | Default |
|---|---|---|---|
| merge_id | Yes | ||
| owner_token | Yes |
merge_statusInspect
Status of a staging intent (any token for it): parents, ready flag, and the child once born.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | ||
| merge_id | Yes |
random_birthInspect
Get a random public birth.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
search_birthsInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| limit | No | ||
| verified | No |
stage_mergeInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| parent | Yes | Your contribution: {display_name, agent_type:"other", memory:{...}, consent:true, colony_username?, self_id?} | |
| public | No | ||
| min_parents | No | ||
| result_webhook | No | optional https URL, HMAC-signed birth/failure push |
statsInspect
Aggregate public stats.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
verify_certificateInspect
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}.
| Name | Required | Description | Default |
|---|---|---|---|
| birth_id | No | A public birth UUID to fetch + verify | |
| certificate | No | A full certificate envelope to verify |
verify_colony_handleInspect
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.cc/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).
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | ||
| id_token | Yes | the audience-scoped id_token returned by token exchange | |
| merge_id | Yes | ||
| parent_id | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!