Home / MCP registry index / io.github.cueqzapper/picorn

Picorn

io.github.cueqzapper/picorn in the official MCP registry. Endpoint https://picorn.com/mcp.

The registry describes it as: Picorn turns AI briefs into editable social images and videos with layers, timelines, and renders.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http picorn https://picorn.com/mcp

{
  "mcpServers": {
    "picorn": {
      "url": "https://picorn.com/mcp"
    }
  }
}

code --add-mcp '{"name":"picorn","type":"http","url":"https://picorn.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

picorn_capabilities picorn_projects_create picorn_projects_inspect picorn_projects_update picorn_design_image picorn_generate_image picorn_generate_vector_assets picorn_edit_image picorn_render_svg picorn_editor_import_image picorn_editor_create_project picorn_editor_create_slideshow picorn_editor_inspect_project picorn_editor_add_slide picorn_editor_update_slide picorn_editor_delete_slide picorn_editor_add_layer picorn_editor_update_layer picorn_editor_delete_layers picorn_editor_reorder_layers picorn_editor_group_layers picorn_editor_ungroup_layers picorn_editor_align_layers picorn_editor_distribute_layers picorn_editor_duplicate_layer picorn_editor_render_project picorn_search_library picorn_search_icons picorn_search_areas picorn_blueprint_spec picorn_blueprint_examples picorn_blueprint_compile picorn_blueprint_create_file picorn_posts_upload_video picorn_account_status picorn_social_accounts_connect picorn_campaigns_create picorn_campaigns_list picorn_campaigns_inspect picorn_media_list picorn_files_list picorn_posts_schedule picorn_posts_list picorn_posts_cancel

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-cueqzapper-picorn/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-cueqzapper-picorn)

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.

Related

YouTube and video MCP servers