Local high-fidelity implementation of Claude Code Artifacts. Provides an HTTP server (localhost:7891) to publish and view HTML and Markdown artifacts with real-time SSE updates. Includes MCP tool for publishing artifacts and a /artifact skill for reopening.
Single tool 'publish_artifact' has a complete input schema with 5 parameters, all typed and described. Description is 189 chars, within the 10-1024 baseline. However, no output schema is documented, the tool returns success/error but the response structure is not specified. Parameter descriptions are adequate but lack constraint details (e.g., max content size is mentioned in description but not in schema). Tool name is clear (verb_noun pattern). No error handling guidance for LLMs (e.g., what to do if publish fails). Risk annotation (WRITE) is present but no idempotent/destructive hints in schema.
Publish an artifact (HTML or Markdown) to the local HTTP server. Accepts title, emoji, content, format, and published_at timestamp. Content is persisted to disk and broadcast to all connected clients via SSE.
No output schema documented. Tool description states content is 'persisted to disk and broadcast to all connected clients via SSE' but does not specify what the tool returns (success object, artifact ID, URL, etc.). LLMs cannot plan downstream actions without knowing the response structure.
No error handling guidance. Description does not explain what happens if content exceeds 16 MiB, if disk write fails, or if SSE broadcast fails. LLMs receive no recovery hints (e.g., 'retry with smaller content' or 'check disk space').
Parameter 'content' lacks explicit max-length constraint in schema. Description mentions '16 MiB' but JSON Schema has no maxLength property. LLMs cannot validate input before calling and may pass oversized payloads.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) in schema. Risk is marked WRITE in metadata but not in the schema itself. Modern MCP clients expect these hints for safety reasoning.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 69 | 2026-07-28+ | v2 |
Parameter 'published_at' is described as 'ISO timestamp' but no format constraint (e.g., 'format': 'date-time') in schema. LLMs may pass invalid timestamps; no validation guidance provided.