Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Authorization not required, issuer https://mcp.doc.farm
Certificate recorded, valid to 2026-12-26
Authorization not required, issuer https://mcp.doc.farm
Added "suggest_link"; changed the definition of "finalize_upload", "host_html_content" and "update_doc_settings" (21 tools before, 22 now)
⟨44 unchanged words⟩ update).","type":"string"},"slug":{"description":"Optional. The link ending the person approved through suggest_link. Same rules as host_html_content.","type":"string"},"upload_path":{"description":"The upload_path value returned ⟨9 unchanged words⟩
⟨155 unchanged words⟩ the standard first time rather than fixing afterwards. Before you publish a NEW doc, call `suggest_link`, show the person the link it returns and ask whether they want a different ending, then pass the ending they settle on as `slug`.
⟨183 unchanged words⟩ several docs match.","type":"boolean"},"slug":{"description":"Optional. The link ending the person approved through suggest_link, the part after the last slash. Only used when this creates a new doc; an update keeps the doc's link. Omit it to make one from the name.","type":"string"}
Unknown → Live
First tool surface recorded: 21 tools (server version 1.0.0)
https://mcp.doc.farm/mcp (mcp_streamable_http) — from mcp_registry, with the record
Showing the latest 7 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
⟨39 unchanged words⟩ pass are changed. Renaming changes the display titleonly;only and keeps thesharelink. To change the linkanditself,slugtheneverpartchangeafter the last slash, pass new_slug. That breaks the old link for everyone who has it, solinksthealreadyfirstsentcallkeepchangesworking.nothing and returns a warning with both links. Pass it on, and only after the person says yes, call again with the same new_slug and confirm_new_link true. Identify the doc via doc_name (fuzzy-matched) or slug.
⟨63 unchanged words⟩ a name.","type":"boolean"},"confirm_new_link":{"description":"Set true only after the person has seen the warning about the old link and said yes.","type":"boolean"},"doc_name":{"description":"Name of the doc (fuzzy-matched). Pass this or slug.","type":"string"},"new_slug":{"description":"A new ending for the share link, the part after the last slash. The old link stops working. Without confirm_new_link nothing changes and you get the warning to pass on.","type":"string"},"notify":{ ⟨60 unchanged words⟩
Suggest a link — The share link a NEW doc would get, before you publish it. People want to see and name their link before it exists, because changing it later breaks the copies already sent. So before host_html_content or finalize_upload creates a new doc, call this with the name you will publish under, show the person the full link, and ask whether they want a different ending, the part after the last slash. Pass the ending they settle on to the publish call as `slug`. Skip the question when they already chose the link or asked you to just publish. To check an ending they suggest, pass it as `slug` here. The…