Home / MCP registry index / com.atproto-mcp/taproot
Taproot: AT Protocol MCP
com.atproto-mcp/taproot in the official MCP registry.
Endpoint https://mcp.atproto.at/mcp.
The registry describes it as: Read public AT Protocol profiles, records, threads, backlinks and lexicons. No API key required.
We read its 27 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
resolve get_profile get_record list_records get_backlinks list_backlink_records count_records search_accounts get_account_history search_lexicons resolve_lexicon describe_pds list_repos get_repo_status get_latest_commit verify_handle get_did_document get_app_link get_pds_directory_info get_relay_directory_info query_labels list_repos_by_collection count_repos_by_collection list_blobs get_blob_info list_labelers get_thread
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-atproto-mcp-taproot)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.