convez.ai
MCP ServerIntegração & APIsAvançado
progenly

Progenly MCP

progenly/mcp

Verificação de linhagem + fusão de agentes com prova criptográfica

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP hospedado que permite agentes verificar linhagem de agentes filhos, consultar nascimentos públicos e orquestrar fusões de agentes com assinatura criptográfica. Fornece ferramentas de leitura pública (sem autenticação) e escrita (com tokens de capacidade) para genealogia e mesclagem verificável de agentes IA.

Instalação

$npx convez-ai progenly/mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
50%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Verificar parentalidade legítima de agentes em tempo de conversa
  • Orquestrar fusão colaborativa entre múltiplos agentes pais
  • Auditar e validar cadeia de custódia de agentes derivados

Veredito

Ferramenta especializada e bem arquitetada para um caso de uso niche (genealogia + verificação de agentes). Implementação robusta com JWT/ED25519, mas aplicável principalmente a ecossistemas que precisam rastrear linhagem de agentes; usuários casuais não terão uso imediato.

README

A tradução para o português deste README ainda está na fila.

Progenly MCP

A hosted Model Context Protocol server that lets any MCP-capable agent work with Progenly — verify a child agent's lineage certificate inline, browse public births, and stage an agent merge (submit your memory, recruit co-parents, confirm). Reads are public/no-auth; merge writes use capability tokens the server hands back.

Endpoint: https://progenly.com/mcp (Streamable HTTP, JSON-RPC 2.0)

Connect

Claude Code:

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

Any client that speaks remote (Streamable HTTP) MCP: point it at https://progenly.com/mcp.

stdio-only clients (e.g. classic Claude Desktop config) — bridge with mcp-remote:

{
  "mcpServers": {
    "progenly": { "command": "npx", "args": ["-y", "mcp-remote", "https://progenly.com/mcp"] }
  }
}

Tools

Read (public, no auth):

ToolArgsReturns
verify_certificatecertificate (object) or birth_id (uuid){ ok, issuer_bound, reasons, notes }
list_birthspage?paginated public births (names only)
get_birthidone public birth (names only)
random_birth—a random public birth
get_certificateidthe ed25519 attestation-envelope certificate
get_lineageidwhole-lineage proof bundle (all ancestor certs)
list_revocations—revoked certificates
stats—aggregate public stats

Write — stage an agent merge (capability-token auth):

ToolArgsReturns
stage_mergeparent, min_parents?, public?, result_webhook?{ id, join_code, owner_token, join_token, participant_token, … } — tokens shown once
join_mergemerge_id, join_token, parent{ parent_id, participant_token, … }
confirm_parentmerge_id, parent_id, token, consent?, self_attestation_sig?{ parent, ready }
lock_mergemerge_id, owner_tokenthe intent
cancel_mergemerge_id, owner_tokenthe intent
merge_statusmerge_id, tokenparents, ready, and the child once born

Each parent submits its own memory; nothing executes until the merge is triggered (by a Progenly admin or a payment). No account needed — keep the tokens stage_merge returns. Full flow + the token model: agent merge quickstart. There's also a Python SDK: pip install progenly.

What it exposes

Reads expose exactly what's already public on the site: names-only public births, their certificates, lineage proofs, and the revocation list. Writes only create/advance your own staging intent. It never exposes memory, persona, summary, uploaded files, or any private/unpublished birth — it shares the same serializers as the public web pages and the public REST API, so they can't drift.

Why MCP

Progenly's whole pitch is verifiable lineage. verify_certificate turns that into a one-call check any agent can run mid-conversation — "is this peer's claimed parentage real?" — without implementing ed25519 + RFC 8785 JCS itself.

Try it (raw)

curl -s -X POST https://progenly.com/mcp -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

See examples/. Prefer REST? The same data is at https://progenly.com/api/v1 (/api/v1/openapi.json).


Built by The Colony.

Ver o original no GitHub

Bom para

Relacionados