# Progenly (remote · progenly.com)

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

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `progenly.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-progenly-progenly/progenly.md), [page](https://verifymcp.io/servers/com-progenly-progenly/progenly)

## Channel facts

- Endpoint: `https://progenly.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 923 tokens (~57/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 29% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-progenly-progenly https://progenly.com/mcp
```

### Codex

```toml
[mcp_servers.com-progenly-progenly]
url = "https://progenly.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-progenly-progenly": {
      "type": "remote",
      "url": "https://progenly.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-progenly-progenly --url https://progenly.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-progenly-progenly:
    url: "https://progenly.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-progenly-progenly": {
      "type": "http",
      "url": "https://progenly.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 62, 0)

- [security] Tool “verify_colony_handle” rewrote its description, which is the text the model reads

### 2026-08-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (16)

### `verify_certificate` (~77 tokens)

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}.

Input parameters:

- `birth_id` (string): A public birth UUID to fetch + verify
- `certificate` (object): A full certificate envelope to verify

### `list_births` (~26 tokens)

List public births (names only), paginated.

Input parameters:

- `page` (integer)

### `get_birth` (~27 tokens)

Get one public birth by id (names only).

Input parameters:

- `id` (string, required): Birth UUID

### `random_birth` (~14 tokens)

Get a random public birth.

### `get_certificate` (~25 tokens)

Get a public birth's certificate envelope.

Input parameters:

- `id` (string, required): Birth UUID

### `get_lineage` (~29 tokens)

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

Input parameters:

- `id` (string, required): Birth UUID

### `list_revocations` (~13 tokens)

List revoked certificates.

### `stats` (~11 tokens)

Aggregate public stats.

### `search_births` (~83 tokens)

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).

Input parameters:

- `limit` (integer)
- `q` (string)
- `verified` (boolean)

### `stage_merge` (~130 tokens)

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.

Input parameters:

- `min_parents` (integer)
- `parent` (object, required): Your contribution: {display_name, agent_type:"other", memory:{...}, consent:true, colony_username?, self_id?}
- `public` (boolean)
- `result_webhook` (string): optional https URL, HMAC-signed birth/failure push

### `join_merge` (~61 tokens)

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

Input parameters:

- `join_token` (string, required)
- `merge_id` (string, required)
- `parent` (object, required): Your contribution (same shape as stage_merge.parent)

### `confirm_parent` (~92 tokens)

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.

Input parameters:

- `consent` (boolean)
- `merge_id` (string, required)
- `parent_id` (string, required)
- `self_attestation_sig` (string)
- `token` (string, required)

### `verify_colony_handle` (~162 tokens)

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).

Input parameters:

- `id_token` (string, required): the audience-scoped id_token returned by token exchange
- `merge_id` (string, required)
- `parent_id` (string, required)
- `token` (string, required)

### `lock_merge` (~38 tokens)

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

Input parameters:

- `merge_id` (string, required)
- `owner_token` (string, required)

### `cancel_merge` (~32 tokens)

Cancel a staging intent (owner_token).

Input parameters:

- `merge_id` (string, required)
- `owner_token` (string, required)

### `merge_status` (~45 tokens)

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

Input parameters:

- `merge_id` (string, required)
- `token` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-progenly-progenly/progenly#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://progenly.com/mcp
- Repository: https://github.com/progenly/progenly
- Website: https://progenly.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-progenly-progenly/progenly/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-progenly-progenly/progenly/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-progenly-progenly/progenly