Home / MCP registry index / app.cannonstudio/cannon-studio
Cannon Studio
app.cannonstudio/cannon-studio in the official MCP registry.
Endpoint https://www.cannonstudio.app/mcp.
The registry describes it as: Public Cannon Studio MCP for product, pricing, workflow, model, and API answers.
We read its 31 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
search fetch list_capabilities recommend_workflow compare_alternatives get_pricing_context list_offerings get_checkout_link get_model_availability list_toolkits get_api_operation api_status estimate_generation_cost create_generation_request get_generation_request list_creator_flow_projects get_creator_flow_project create_creator_flow_project update_creator_flow_project delete_creator_flow_project export_creator_flow_project list_worlds get_world create_world update_world delete_world list_world_assets get_world_asset create_world_asset update_world_asset delete_world_asset
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-cannonstudio-cannon-studio)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.