Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Progenly

REMOTE · PROGENLY.COM · SCANNED AUG 3

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

Available components

+5 this week 63 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 923 tokens (~57/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 29% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · progenly.com

# add to Claude Code
claude mcp add --transport http com-progenly-progenly https://progenly.com/mcp
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-progenly-progenly --url https://progenly.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-progenly-progenly:
    url: "https://progenly.com/mcp"
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +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.

  • 2 Aug 26 0
    • Tool “verify_colony_handle” rewrote its description, which is the text the model reads security
  • 1 Aug 26 +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.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +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.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://progenly.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.progenly.com CN=YR2,O=Let's Encrypt,C=US 14 Jun 2026 12 Sept 2026 RSA 2048 SHA256-RSA 545cb5dac7a853219c32738a94af9b3cc1a
SANs: mail.progenly.com, progenly.com, www.progenly.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of progenly.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
progenly.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://progenly.com/mcp Verified 200
http (plaintext) http://progenly.com/mcp HTTPS enforced 301 https://progenly.com/mcp
MCP tools — 16 exposed · ~865 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
cancel_merge ~32

Cancel a staging intent (owner_token).

NameTypeReqDescription
merge_idstringyes
owner_tokenstringyes

No output schema declared.

No examples provided.

confirm_parent ~92

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.

NameTypeReqDescription
consentboolean
merge_idstringyes
parent_idstringyes
self_attestation_sigstring
tokenstringyes

No output schema declared.

No examples provided.

get_birth ~27

Get one public birth by id (names only).

NameTypeReqDescription
idstringyesBirth UUID

No output schema declared.

No examples provided.

get_certificate ~25

Get a public birth's certificate envelope.

NameTypeReqDescription
idstringyesBirth UUID

No output schema declared.

No examples provided.

get_lineage ~29

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

NameTypeReqDescription
idstringyesBirth UUID

No output schema declared.

No examples provided.

join_merge ~61

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

NameTypeReqDescription
join_tokenstringyes
merge_idstringyes
parentobjectyesYour contribution (same shape as stage_merge.parent)

No output schema declared.

No examples provided.

list_births ~26

List public births (names only), paginated.

NameTypeReqDescription
pageinteger

No output schema declared.

No examples provided.

list_revocations ~13

List revoked certificates.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lock_merge ~38

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

NameTypeReqDescription
merge_idstringyes
owner_tokenstringyes

No output schema declared.

No examples provided.

merge_status ~45

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

NameTypeReqDescription
merge_idstringyes
tokenstringyes

No output schema declared.

No examples provided.

random_birth ~14

Get a random public birth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_births ~83

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

NameTypeReqDescription
limitinteger
qstring
verifiedboolean

No output schema declared.

No examples provided.

stage_merge ~130

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.

NameTypeReqDescription
min_parentsinteger
parentobjectyesYour contribution: {display_name, agent_type:"other", memory:{...}, consent:true, colony_username?, self_id?}
publicboolean
result_webhookstringoptional https URL, HMAC-signed birth/failure push

No output schema declared.

No examples provided.

stats ~11

Aggregate public stats.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_certificate ~77

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

NameTypeReqDescription
birth_idstringA public birth UUID to fetch + verify
certificateobjectA full certificate envelope to verify

No output schema declared.

No examples provided.

verify_colony_handle ~162

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

NameTypeReqDescription
id_tokenstringyesthe audience-scoped id_token returned by token exchange
merge_idstringyes
parent_idstringyes
tokenstringyes

No output schema declared.

No examples provided.