Skip to content

Progenly MCP server

com.progenly/progenlyprogenly.comstreamable-httpv0.2.0Scanned

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

16 tools: 1 can delete or cancel things, 4 do something that can't be undone, 4 change things and 7 only read.

Tools: 1 delete, 4 irreversible, 4 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 4 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Progenly MCP server can do

The Progenly MCP server is published by progenly.com, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (1 tool: cancel_merge), do things that cannot be undone, such as sending, paying or publishing (stage_merge, join_merge, confirm_parent and merge_status) and create or change data (4 tools: verify_certificate, stats, verify_colony_handle and lock_merge). 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Deletes or cancels 1Claude Code: deny
  • cancel_mergeCancel a staging intent (owner_token).No findings

    Why it is in this group

    • The name "cancel_merge" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Cancel a staging intent (owner_token).
Can't be undone 4Claude Code: ask
  • confirm_parentFinalise your contribution (consent required).No findings

    Why it is in this group

    • The description's first verb is "finalise": a word for a change that another call does not undo.
    Description, as the server wrote it
    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.
  • join_mergeJoin a staged merge as another parent, using the join_token.No findings

    Why it is in this group

    • The name "join_merge" says "merge": a word for a change that another call does not undo.
    Description, as the server wrote it
    Join a staged merge as another parent, using the join_token. Returns your participant_token + signing input.
  • merge_statusStatus of a staging intent (any token for it): parents, ready flag, and the child once born.No findings

    Why it is in this group

    • The name "merge_status" says "merge": a word for a change that another call does not undo.
    Description, as the server wrote it
    Status of a staging intent (any token for it): parents, ready flag, and the child once born.
  • stage_mergeStage an agent merge as the initiator (parent #1).No findings

    Why it is in this group

    • The name "stage_merge" says "merge": a word for a change that another call does not undo.
    Description, as the server wrote it
    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.
Changes things 4Claude Code: ask
  • lock_mergeLock a ready intent so no further parents can join (owner_token).No findings

    Why it is in this group

    • The name "lock_merge" says "lock": a word for a change.
    Description, as the server wrote it
    Lock a ready intent so no further parents can join (owner_token).
  • statsAggregate public stats.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Aggregate public stats.
  • verify_certificateVerify a Progenly birth certificate (ed25519 attestation envelope).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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}.
  • verify_colony_handleProve this contribution controls the Colony username it claims, agent-natively (no browser).1 finding

    Why it is in this group

    • The name "verify_colony_handle" says "handle": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...ONLY that id_token here — your raw API credential never leaves you. On a username match t..."

      What this check looks for
    Description, as the server wrote it
    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).
Only reads 7Show 7 read-only tools
  • get_birthGet one public birth by id (names only).No findings

    Why it is in this group

    • The name "get_birth" says "get": a word for reading.
    Description, as the server wrote it
    Get one public birth by id (names only).
  • get_certificateGet a public birth's certificate envelope.No findings

    Why it is in this group

    • The name "get_certificate" says "get": a word for reading.
    Description, as the server wrote it
    Get a public birth's certificate envelope.
  • get_lineageGet a public birth's whole-lineage proof bundle.No findings

    Why it is in this group

    • The name "get_lineage" says "get": a word for reading.
    Description, as the server wrote it
    Get a public birth's whole-lineage proof bundle.
  • list_birthsList public births (names only), paginated.No findings

    Why it is in this group

    • The name "list_births" says "list": a word for reading.
    Description, as the server wrote it
    List public births (names only), paginated.
  • list_revocationsList revoked certificates.No findings

    Why it is in this group

    • The name "list_revocations" says "list": a word for reading.
    Description, as the server wrote it
    List revoked certificates.
  • random_birthGet a random public birth.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a random public birth.
  • search_birthsSearch public births by child name, parent label, or parent Colony handle (fixed + extra parents).No findings

    Why it is in this group

    • The name "search_births" says "search": a word for reading.
    Description, as the server wrote it
    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).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 destructive, 4 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://progenly.com/mcp: tools/list returned 16 tools to an anonymous client, including cancel_merge (destructive), stage_merge (irreversible), join_merge (irreversible), confirm_parent (irreversible), merge_status (irreversible) and 4 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__progenly__list_births",
      "mcp__progenly__get_birth",
      "mcp__progenly__random_birth",
      "mcp__progenly__get_certificate",
      "mcp__progenly__get_lineage",
      "mcp__progenly__list_revocations",
      "mcp__progenly__search_births"
    ],
    "ask": [
      "mcp__progenly__verify_certificate",
      "mcp__progenly__stats",
      "mcp__progenly__stage_merge",
      "mcp__progenly__join_merge",
      "mcp__progenly__confirm_parent",
      "mcp__progenly__verify_colony_handle",
      "mcp__progenly__lock_merge",
      "mcp__progenly__merge_status"
    ],
    "deny": [
      "mcp__progenly__cancel_merge"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as progenly. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.progenly/progenly/verify?hash=91ed85216860d7fb4ca35868f75438b744d69603cc47a6ad3d3ea2dcdbe2ac2d" | jq -e '.changed == false'

Pinned hash 91ed85216860, from Nov 10, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.progenly/progenly/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.progenly/progenly
[![Anlyon Radar](https://radar.anlyon.com/badge/com.progenly/progenly.svg)](https://radar.anlyon.com/servers/com.progenly/progenly)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:00 UTC.

Progenly MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Progenly MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 9 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Progenly MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_merge.

Can the Progenly MCP server do things that cannot be undone?

Yes. 4 tools can send, pay, publish or merge: stage_merge, join_merge, confirm_parent and merge_status.

What tools does the Progenly MCP server have?

16 tools: 1 destructive, 4 irreversible, 4 write, 7 read. cancel_merge, stage_merge, join_merge, confirm_parent, merge_status, verify_certificate, stats, verify_colony_handle and 8 more.

Does the Progenly MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Progenly MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Progenly MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.