Home / MCP registry index / com.viberooster/hatch
Hatch
com.viberooster/hatch in the official MCP registry.
Endpoint https://mcp.theroost.dev/mcp. Source: github.com/VibeRooster/viberooster.github.io.
The registry describes it as: Hosting for AI agents: publish a live website in one tool call, ephemeral or forever.
We read its 24 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
hatch upload lookup list rename_org convert catalog list_templates checkout poll_checkout auth share await_decision continue_decision poll_decision whoami get_pairing_code poll_pairing refresh_session poll_approval alarm squawk_request_access squawk_poll_access deploy
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-viberooster-hatch)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.