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

REMOTE · PLACEPACK.TOP · 2 COMPONENTS

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

−87 this week 0 Trust /100

Last scanned (23 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 22 Oct 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security3
  • TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
  • Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • DNSSEC
  • Transport

Checks we could not complete (9)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 29 Oct 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 28 Oct 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 27 Oct 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 26 Oct 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 25 Oct 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 24 Oct 26 0
    • HTTPS: pass → unverified ▼ security
    • DNSSEC: unverified → pass ▲ security
  • 23 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
  • 1 Oct 26 +62
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
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 29 Oct 2026 · Probed https://placepack.top/mcp

TLS unreached
DNSSEC secure

Validation of placepack.top. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
top. DS published 41508 13 Verified
placepack.top. DS published 17642 13 Verified
placepack.top. Verified address RRset verified with the apex keys
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://placepack.top/mcp Unreachable
http (plaintext) http://placepack.top/mcp Inconclusive 404
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
bgColorstring–Background hex color, with or without #.
formatstring––
paddingnumber––
specstringyesSize spec such as 800x600.svg, hero:1600x900, or thumb:420x247@2x.
strokeWidthnumber––
templatestring–Label template. Tokens: {alias}, {w}, {h}, {ratio}, {index}, {bg}, {color}.
textColorstring–Label 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
bgColorstring–Background hex color, with or without #.
formatstring––
inlineZipboolean–Return a base64 ZIP for SVG packs with at most 10 files.
paddingnumber––
presetstring–Preset key such as og, developers, automation, or favicon.
sizesstring–Newline-separated size specs.
strokeWidthnumber––
templatestring–Label template. Tokens: {alias}, {w}, {h}, {ratio}, {index}, {bg}, {color}.
textColorstring–Label 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.

Install

How do I install the PlacePack MCP server?

PlacePack is a hosted endpoint at https://placepack.top/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · placepack.top

# add to Claude Code
claude mcp add --transport http top-placepack-placepack 'https://placepack.top/mcp'
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 hosted endpoint (https://placepack.top/mcp).

Is the PlacePack MCP server safe to use?

PlacePack scores 0 out of 100 on VerifyMCP. 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.

Does the PlacePack MCP server require authentication?

Its publisher declares no required credentials for PlacePack. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the PlacePack MCP server still maintained?

PlacePack has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the PlacePack MCP server?

VerifyMCP ran 2 checks on PlacePack, covering DNSSEC and Transport. 9 items could not be completed, a gap on our side rather than a finding about PlacePack: TLS certificate, Authorization, HTTPS, HSTS header and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.