Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PlacePack

NPM · @MARTINTOZ/PLACEPACK-MCP · 2 COMPONENTS · SCANNED SEP 22

Generate deterministic placeholder image URLs and packs for docs, staging, testing, and AI agents.

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 390 tokens (~78/item across 5 items; 3 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the PlacePack MCP server?

PlacePack runs locally as an npm package, launched with npx -y @martintoz/placepack-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @martintoz/placepack-mcp

# add to Claude Code
claude mcp add top-placepack-placepack -- npx -y @martintoz/placepack-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "top-placepack-placepack": {
      "command": "npx",
      "args": [
        "-y",
        "@martintoz/placepack-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "top-placepack-placepack": {
      "command": "npx",
      "args": [
        "-y",
        "@martintoz/placepack-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add top-placepack-placepack -- npx -y @martintoz/placepack-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "top-placepack-placepack": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@martintoz/placepack-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add top-placepack-placepack --command npx --arg -y --arg @martintoz/placepack-mcp
# ~/.hermes/config.yaml
mcp_servers:
  top-placepack-placepack:
    command: "npx"
    args: ["-y", "@martintoz/placepack-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "top-placepack-placepack": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@martintoz/placepack-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add top-placepack-placepack -t stdio -c npx -a -y @martintoz/placepack-mcp
// mcp.json
{
  "mcpServers": {
    "top-placepack-placepack": {
      "command": "npx",
      "args": [
        "-y",
        "@martintoz/placepack-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Analysed npm/@martintoz/placepack-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~356 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
placepack_create_image ~151

Validate one size spec and return an embeddable PlacePack image URL, filename, Markdown, and HTML.

NameTypeReqDescription
bgColorstringBackground hex color, with or without #.
formatstring
paddingnumber
specstringyesSize spec such as 800x600.svg, hero:1600x900, or thumb:420x247@2x.
strokeWidthnumber
templatestringLabel template. Tokens: {alias}, {w}, {h}, {ratio}, {index}, {bg}, {color}.
textColorstringLabel hex color, with or without #.

No output schema declared.

No examples provided.

placepack_create_pack ~179

Validate multiple size specs or one preset and return a manifest of generated PlacePack image URLs. Optionally inline a small SVG ZIP as base64.

NameTypeReqDescription
bgColorstringBackground hex color, with or without #.
formatstring
inlineZipbooleanReturn a base64 ZIP for SVG packs with at most 10 files.
paddingnumber
presetstringPreset key such as og, developers, automation, or favicon.
sizesstringNewline-separated size specs.
strokeWidthnumber
templatestringLabel template. Tokens: {alias}, {w}, {h}, {ratio}, {index}, {bg}, {color}.
textColorstringLabel hex color, with or without #.

No output schema declared.

No examples provided.

placepack_list_presets ~26

Return named PlacePack size presets with labels, specs, and default formats.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the PlacePack MCP server?

PlacePack is an MCP server listed in the public MCP registry as top.placepack/placepack. Generate deterministic placeholder image URLs and packs for docs, staging, testing, and AI agents. This page covers its npm package (@martintoz/placepack-mcp).

Is the PlacePack MCP server safe to use?

PlacePack scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PlacePack MCP server expose?

PlacePack exposes 3 tools: placepack_list_presets, placepack_create_image, placepack_create_pack. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.

Is the PlacePack MCP server still maintained?

PlacePack is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the PlacePack MCP server under?

PlacePack declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.