Home / MCP registry index / ac.tandem/docs-mcp
ac.tandem/docs-mcp
ac.tandem/docs-mcp in the official MCP registry.
Endpoint https://tandem.ac/mcp. Source: github.com/frumu-ai/tandem.
The registry describes it as: Remote MCP server for Tandem docs, install guides, SDKs, workflows, and agent setup help.
We read its 13 tools on 2026-10-21. 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
search_docs get_doc get_start_path recommend_next_docs answer_how_to get_tandem_guide warmup_docs_cache get_docs_cache_status refresh_docs_index refresh_doc_page invalidate_docs_cache compare_docs_index_refresh compare_doc_page_refresh
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ac-tandem-docs-mcp)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.