MCP.Market

Wall Marketing MCP server

online · 100% uptime
by wall.marketing·marketing.wall/platform·v1.1.1

Book ads on e-paper screens in venues, or earn commission signing venues up as an ambassador.

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Wall Marketing yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Wall Marketing tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Wall Marketing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
340 ms
faster than 43% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-16, latest 2026-10-17, typically one every 1 day.

Install Wall Marketing in Claude Code, Cursor or VS Code

claude mcp add --transport http platform https://www.wall.marketing/mcp
Add to Cursor

Wall Marketing: common questions

Is Wall Marketing MCP server safe?
Mostly: it is graded B (77/100). Read the Wall Marketing safety report
How do I install Wall Marketing?
It runs remotely at www.wall.marketing. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Wall Marketing need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Wall Marketing maintained?
The latest release is v1.1.1.
Is Wall Marketing up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Wall Marketing compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 340 ms (faster than 43% of 30,031 servers). Full comparison.