Ir para o conteúdo
Logo de Taproot MCP

Servidor MCP de Taproot MCP

Quais servidores MCP são de Taproot MCP, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-24

← Voltar para Taproot MCP

De quem é o servidor
  • Nome no registrocom.atproto-mcp/taprootverificado no registro MCP

O nome no registro fica sob atproto-mcp.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-24
  • Estadorespondeverificado em 2026-10-24
  • Ferramentas27
  • O servidor se chamataproot
  • Versão do servidor0.1.0
  • Versão do protocolo2025-06-18

Em 2026-10-24 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 925 ms.

Um agente deve conectá-loConectar
  • As ferramentas fazem todos os casos de uso verificados: Look up public accounts across the AT Protocol network; Browse public records and conversations from network apps; Inspect lexicon schemas that network apps use.

Depois de conectar

  • Para "Look up public accounts across the AT Protocol network", a primeira chamada provável é search_accounts.
  • Para "Inspect lexicon schemas that network apps use", a primeira chamada provável é search_lexicons.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

Medido todo diaverificações diárias: 9, a primeira em 2026-10-24
  • Nota INITE MCP98 de 100responde 100 · faz o trabalho 100 · definições 100 · contexto 85 · conexão 100
  • O que um agente consegue fazer com ele3 de 3 casos de uso
  • Respondeuem 100% dos dias9 de 9 verificações diárias
  • Mediana da primeira resposta651 ms
  • Espaço no contexto do agente≈ 5.283 tokensas definições de todas as ferramentas (27), que o agente carrega a cada turno
  • Definições das ferramentasA · 100 de 100
  • Resultados tipados27 de 27 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
  • Todas as ferramentas passam nas seis verificações.

O que um agente consegue fazer com ele

  • consegue · Look up public accounts across the AT Protocol network
  • consegue · Browse public records and conversations from network apps
  • consegue · Inspect lexicon schemas that network apps use

Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?

Vale conferir

Nenhum dos cinco sinais de alerta nestas definições.

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

Ferramentas que oferece27 ferramentas · lido em 2026-10-24
  • resolve

    Resolve any AT Protocol identifier to JSON. Accepts an at:// URI (at://<did-or-handle>/<collection>/<rkey>), a bare handle (alice.bsky.social), or a DID (did:plc:...). Returns a profile, a collection page, or a single record depending on…

  • get_profile

    Get an account's repository overview (handle, DID, PDS, and the list of collections it contains). Input is a handle or DID.

  • get_record

    Fetch a single record by its full at:// URI (must include collection and rkey). Returns the record's value, CID, and resolved identity.

  • list_records

    List records in a collection for an account, with pagination. Provide the repo (handle or DID) and the collection NSID (e.g. app.bsky.feed.post).

  • get_backlinks

    Index of who/what references a target,the inbound likes, reposts, quotes, replies, and follows,as COUNTS per category, via the Constellation backlink index. Target is a record's at:// URI or an account DID. This returns aggregate counts…

  • list_backlink_records

    List the actual records (author DID + verified handle + at:// URI, newest first) that reference a target for ONE category,i.e. WHO liked, reposted, quoted, replied to, mentioned, or follows it. Workflow: call get_backlinks first to get a…

  • count_records

    Count the total records in an account's collection (e.g. how many likes a user has given). Scans server-side so you don't page manually. AT Protocol has no cheap exact count, so for very large collections this returns exact:false with a…

  • search_accounts

    Search for AT Protocol accounts by handle or display name (paginated, via the Bluesky AppView app.bsky.actor.searchActors, so accounts unknown to that index may be missing). Returns candidate accounts with DID + handle, to turn a name…

  • get_account_history

    An account's history from its PLC audit log: handle changes, PDS migrations, signing-key rotations, and creation time. did:plc accounts only (did:web has no PLC log). Input is a handle or DID.

  • search_lexicons

    Browse or search the registry of published AT Protocol lexicon schemas. The response's `total` field is the exact registry size and `matched` is the exact match count. Substring matches the NSID or description (query 'profile' → anything…

  • resolve_lexicon

    Explain what a record type means by resolving its lexicon schema. Input is a collection NSID (e.g. app.bsky.feed.post). Returns the schema's description and definition.

  • describe_pds

    Describe a Personal Data Server: its DID, whether registration requires an invite, the handle domains you can register there, and ToS/contact links. Works for any PDS, not just Bluesky. Input is the PDS origin (e.g…

  • list_repos

    List the accounts (repositories) hosted on a PDS, via com.atproto.sync.listRepos: each repo's DID and active/takedown status, paginated. Answers 'who is hosted on this PDS?' / 'how many accounts does this PDS have?'. By default returns…

  • get_repo_status

    Liveness/moderation status of an account's repository: whether it is active, its current revision, and any takedown/suspended/deactivated/deleted state. Answers 'has @alice been taken down?' which get_profile can't. Input is a handle or…

  • get_latest_commit

    The current head commit of an account's repository (com.atproto.sync.getLatestCommit): its commit CID and revision. The cheapest way to fingerprint a repo or detect whether it changed since you last looked, without downloading data…

  • verify_handle

    Bidirectionally verify that a handle is really owned by its DID, via DNS TXT and HTTPS well-known. Returns whether each method passed. Use this to check for impersonation/spoofing,search results and resolve give candidates, this gives…

  • get_did_document

    Fetch the raw DID document for any DID or handle: all aliases (alsoKnownAs), every service entry (PDS, labeler, custom AppView), and verification methods. Broader than get_profile, and works for did:web accounts. Input is a handle or DID.

  • get_app_link

    Turn an at:// URI (or handle/DID) into shareable web links,a Bluesky/Blacksky app URL to open in a browser, plus the canonical PDS getRecord URL. Use when the user wants a clickable/pasteable link.

  • get_pds_directory_info

    A cached health card for a PDS from pds.directory: version, DID, approximate user count, reachability, last-checked time, available domains, and which relays index it. Input is the PDS hostname (e.g. pds.example.com). Best-effort/cached…

  • get_relay_directory_info

    A cached overview of a relay from firehose.directory: counts of PDSes it indexes (total/active/offline/banned) and total accounts. Input is the relay hostname (e.g. bsky.network). Best-effort/cached data.

  • query_labels

    What moderation labels a labeler has applied to a subject (com.atproto.label.queryLabels),e.g. 'has @alice or this post been labeled spam/nsfw/hidden by labeler X?'. Anonymous and service-agnostic: the labeler's own service endpoint is…

  • list_repos_by_collection

    Network-wide: which accounts publish a given collection/lexicon,e.g. 'who has an app.bsky.feed.generator (a custom feed)?' or who uses a custom lexicon. Via a relay's com.atproto.sync.listReposByCollection (anonymous). By default returns…

  • count_repos_by_collection

    Count how many accounts across the network publish a given collection/lexicon,e.g. 'how many accounts have an at.glean.subscription?'. Walks a relay's com.atproto.sync.listReposByCollection with NO per-account handle resolution, so it's…

  • list_blobs

    List the blobs (uploaded media/attachments,images, video, etc.) hosted in an account's repository, via com.atproto.sync.listBlobs. Returns each blob's CID and its canonical PDS getBlob URL (PDS-native, works for any PDS,not a CDN)…

  • get_blob_info

    Get metadata for a single blob: its canonical PDS getBlob URL plus a best-effort content-type and byte size (via a HEAD request). Returns the URL, never the bytes. Use to turn a blob ref (CID) found in a record into a downloadable link…

  • list_labelers

    List the labeler (moderation) services known to the labeler relay,each labeler's DID, resolved handle, and service endpoint. The discovery step BEFORE query_labels, which needs a labeler DID/handle up front: use this to find…

  • get_thread

    Reconstruct the conversation around a post: its ancestor chain up to the thread root (following reply.parent, root-first) PLUS a bounded descendant reply TREE,replies, replies-to-replies, and so on, each tagged with its depth and…

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

{
  "mcpServers": {
    "taproot": {
      "type": "http",
      "url": "https://mcp.atproto.at/mcp"
    }
  }
}

Adicionar

Claude Code, no terminal

claude mcp add --transport http atproto-mcp https://mcp.atproto.at/mcp

Adicionar ao CursorAdicionar ao VS Code

claude.ai, ChatGPT e outros clientes: adicione https://mcp.atproto.at/mcp como conector personalizado nas configurações.

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.