Home / MCP registry index / com.attachpage/attachpage
AttachPage
com.attachpage/attachpage in the official MCP registry.
Endpoint https://attachpage.com/mcp.
The registry describes it as: Publish webpages and documents, send private review links, and collect comments and approvals.
We read its 11 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
publish_document get_profile publish_anonymous_page publish_page send_page list_pages get_page update_page get_feedback resolve_feedback notify_recipients
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-attachpage-attachpage)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.