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.

The Button Wall

NPM · BUTTONWALL-MCP

Rent a clickable button on a million-pixel wall: find free space, get a quote, create a checkout.

Available components

66 Trust /100

Last scanned (11 hours ago)

Scores higher than 38% of npm servers

Category E-commerce

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 Security98
  • 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
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 476 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 32% 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 4 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 15 Oct 26 +28
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 32 functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
  • 14 Oct 26 38

    First indexed and scored.

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 18 Oct 2026 · Analysed npm/buttonwall-mcp@0.1.1

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 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~476 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
create_checkout_link ~237

Creates a Stripe checkout link for a new button. Nothing is charged by this call: the link must be opened and paid by the human buyer, and the button goes live only after a person at The Button Wall reviews it (full refund if rejected). Confirm size, position, plan, price, text and link with the user before calling. Call once per purchase: checkout links are rate-limited (10 per 10 minutes).

NameTypeReqDescription
bg_colorstring––
bg_color_end––Optional gradient end colour.
emailstringyesBuyer's email; receipts and the private manage link go here.
height_px–yes–
labelstringyesButton text (the call to action).
planstringyes1m = 30 days, 6m = 180 days (−10%), 12m = 360 days (−20%)
show_faviconboolean––
text_colorstring––
urlstringyes–
width_pxintegeryes–
x_pxintegeryes–
y_pxintegeryes–

No output schema declared.

No examples provided.

find_free_spots ~75

Free positions that fit a button of the given size, nearest to a preferred point first (default: the centre of the wall).

NameTypeReqDescription
height_px–yes–
limitinteger––
near_x_pxinteger––
near_y_pxinteger––
width_pxintegeryes–

No output schema declared.

No examples provided.

get_wall_status ~44

How full The Button Wall is right now, plus pricing rules. The wall is 1000×1000 px; spots are rented in 10×10 px blocks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quote_spot ~120

Price for a button of a given size and plan, and whether that exact position is free.

NameTypeReqDescription
height_px–yes–
planstringyes1m = 30 days, 6m = 180 days (−10%), 12m = 360 days (−20%)
width_pxintegeryes–
x_pxinteger–Left edge in px (multiple of 10). Omit to only get the price.
y_pxinteger–Top edge in px (multiple of 10).

No output schema declared.

No examples provided.

Install

How do I install the The Button Wall MCP server?

The Button Wall runs locally as an npm package, launched with npx -y buttonwall-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 · buttonwall-mcp

# add to Claude Code
claude mcp add leovenom-buttonwall -- npx -y buttonwall-mcp
Common questions

What is the The Button Wall MCP server?

The Button Wall is an MCP server listed in the public MCP registry as io.github.leovenom/buttonwall. Rent a clickable button on a million-pixel wall: find free space, get a quote, create a checkout. This page covers its npm package (buttonwall-mcp).

Is the The Button Wall MCP server safe to use?

The Button Wall scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 The Button Wall MCP server expose?

The Button Wall exposes 4 tools: get_wall_status, quote_spot, find_free_spots, create_checkout_link. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

Is the The Button Wall MCP server still maintained?

The Button Wall is still listed as active in the MCP registry. We last reached this channel on 18 October 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 The Button Wall MCP server under?

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