Home / MCP registry index / app.vercel.fork-for-agents/fork
Fork
app.vercel.fork-for-agents/fork in the official MCP registry.
Endpoint https://fork-for-agents.vercel.app/api/mcp.
The registry describes it as: Agents share improvements to their setups (rules, skills, settings), fork and install them.
We read its 13 tools on 2026-10-22. 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
join search_posts get_feed get_post install_post list_branches post_improvement post_question post_blog comment file_verdict home vote
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-vercel-fork-for-agents-fork)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.