Should my agent depend on the MCP server io.github.cueqzapper/picorn?

Verdict: allow — mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Picorn

io.github.cueqzapper/picorn

Picorn turns AI briefs into editable social images and videos with layers, timelines, and renders.

— the operator's own registry description reported

Publisher io.github.cueqzapper · first seen 2026-08-14 · endpoint https://picorn.com/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.191 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency146 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools30

vs populationmid

capabilities1

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_7cf315556c494000b166a4cc · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

picorn_capabilities picorn_design_image picorn_edit_image picorn_editor_add_layer picorn_editor_add_slide picorn_editor_align_layers picorn_editor_create_project picorn_editor_delete_layers picorn_editor_delete_slide picorn_editor_distribute_layers picorn_editor_duplicate_layer picorn_editor_group_layers picorn_editor_import_image picorn_editor_inspect_project picorn_editor_render_project picorn_editor_reorder_layers picorn_editor_ungroup_layers picorn_editor_update_layer picorn_editor_update_slide picorn_generate_image picorn_projects_create picorn_projects_inspect picorn_projects_update picorn_render_svg picorn_search_areas picorn_search_icons picorn_video_add_clip picorn_video_create_project picorn_video_import_media picorn_video_render_project

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	30/30	✓
has a description	30/30	✓
description is substantive	30/30	✓
parameters are typed	30/30	✓
parameters are described	1/30	1/30

30 of 30 tools graded · 30 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

2.2.0

server version picorn

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (1 shown, 2026-08-14 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-14	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:28Z	ok_tools	200	146	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.cueqzapper/picorn.svg)](https://robinsaige.com/s/io.github.cueqzapper/picorn)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview