Home / MCP registry index / app.2ools/mcp
2ools
app.2ools/mcp in the official MCP registry.
Endpoint https://2ools.app/mcp. Source: github.com/2ools/mcp-server.
The registry describes it as: Build, version, review, and export websites, web apps, and games from a conversation.
We read its 81 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
create_public_preview list_build_systems list_connected_engines get_project_engine_workspace attach_project_engine_workspace register_existing_project build_from_conversation start_project_on_engine refine_project get_build get_engine_dispatch compare_versions list_approval_requests approve_version reject_version cancel_build get_account_profile update_account_profile get_project_access invite_project_member update_project_member_role remove_project_member revoke_project_invite list_projects get_project get_project_context continue_project refresh_project_cockpit activate_project get_project_mission get_project_intelligence update_project_intelligence get_project_discipline list_project_engineering_decisions answer_project_engineering_decision manage_project_discipline update_project_mission review_project_mission manage_work_watchdog act_on_project_os_task update_living_plan render_project_preview list_project_agents get_agent run_project_agent get_project_agent_mode configure_project_agent_mode advance_project_agent_mode dispatch_project_work get_project_work_dispatch cancel_agent_run get_project_activity wait_for_project_activity list_project_feedback add_project_feedback resolve_project_feedback list_project_pins add_project_pin remove_project_pin prepare_version_export and 21 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-2ools-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.