Skip to content

Cellionaire MCP server

com.cellionaire/wallcellionaire.comstreamable-httpv1.0.0Scanned

Read the 1000x1000 Cellionaire pixel wall and create USDC orders for cells; you pay on-chain.

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Cellionaire MCP server can do

The Cellionaire MCP server is published by cellionaire.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (4 tools: wall_overview, check_cells_available, prepare_x402_order and create_order), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 4Claude Code: ask
  • check_cells_availablePrice a selection of cells right now and say whether it can be ordered (meets the minimum, not reserved, not in image review).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Price a selection of cells right now and say whether it can be ordered (meets the minimum, not reserved, not in image review). Nothing is reserved or charged. Wraps POST /api/quote. Wall coordinates: x 0..999 (left to right), y 0..999 (top to bottom); cell index = y*1000 + x.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_orderCreate an order for cells and return the USDC payment details (recipient wallet, token, amount_units, Solana reference, pay_by, status URL).No findings

    Why it is in this group

    • The name "create_order" says "create": a word for a change.
    Description, as the server wrote it
    Create an order for cells and return the USDC payment details (recipient wallet, token, amount_units, Solana reference, pay_by, status URL). This tool does not pay: the caller sends the USDC transfer itself before pay_by. Same validation and limits as the website (minimum cells, at most 16 colours (image orders are not supported here), rate limits, unpaid-order cap per IP: creating another automatically cancels your oldest unpaid order that has no payment seen; do not pay a cancelled order, payments to it are refunded per the refund policy, and under $1 is not refunded). accepted_terms must be true and means you accept the terms at https://cellionaire.com/terms. Wall coordinates: x 0..999 (left to right), y 0..999 (top to bottom); cell index = y*1000 + x. If you can pay with x402, use prepare_x402_order instead (one request, no transfer to build). If you have no wallet, give status_url to a human.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • prepare_x402_orderPrice cells and return a ready-to-send x402 request (URL, method, headers, JSON body, exact amount).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Price cells and return a ready-to-send x402 request (URL, method, headers, JSON body, exact amount). Nothing is reserved or charged. Send it with an x402 client (x402-fetch, x402-axios, @x402/fetch); it pays and creates the order in one request. Raise the client's max amount if the price is above its default cap (x402-fetch 0.10 USDC, @x402/fetch 1 USDC). Cells that already have an owner can be bought over at the overwrite price (get_wall_info prices.rule: the multiplier times the last price while the cell is inside its reset window, otherwise the empty-cell price); total_usd here, and the 402 of the returned request, state the exact amount. Areas map to the HTTP body as [y*1000+x, 0xRRGGBB] pairs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • wall_overviewCurrent wall version, the URL of the full-wall PNG (1 pixel = 1 cell; alpha 0 empty, 255 bought, 254 site-owned house art) and how to read regions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Current wall version, the URL of the full-wall PNG (1 pixel = 1 cell; alpha 0 empty, 255 bought, 254 site-owned house art) and how to read regions. Wraps GET /api/wall. No input.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_order_statusStatus of an order and its USDC payment (state, received, confirmations, refunds).No findings

    Why it is in this group

    • The name "get_order_status" says "get": a word for reading.
    Description, as the server wrote it
    Status of an order and its USDC payment (state, received, confirmations, refunds). usdc.remaining is an amount to send only when usdc.can_topup is true, or when state is waiting (then it is the one full amount). If can_topup is false after a payment was seen, remaining is omitted: do not send a second transfer. Wraps GET /api/order/{id}. status: pending, processing, paid, pending_review, expired, cancelled, late_paid, refund_pending, refunded, failed.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_wall_infoRules, prices, size, minimum order, payment networks, terms version and whether purchases are open.No findings

    Why it is in this group

    • The name "get_wall_info" says "get": a word for reading.
    Description, as the server wrote it
    Rules, prices, size, minimum order, payment networks, terms version and whether purchases are open. Numbers come from the live settings. No input.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_regionPixels and owners of a rectangle (w*h <= 10000).No findings

    Why it is in this group

    • The name "read_region" says "read": a word for reading.
    Description, as the server wrote it
    Pixels and owners of a rectangle (w*h <= 10000). format "json" (default): base64 RGBA pixels plus runs of empty / buyer (with public display name) / house cells. format "png": the rectangle as a PNG image. Wraps GET /api/region. Wall coordinates: x 0..999 (left to right), y 0..999 (top to bottom); cell index = y*1000 + x.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:22 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cellionaire.com/mcp: tools/list returned 7 tools to an anonymous client, including wall_overview (write), check_cells_available (write), prepare_x402_order (write), create_order (write)

    What this check looks for

Posture changes

  1. Nov 12, 2026
    • Tools that change things, listed without credentials: 3 to 4

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 3 changed.+1 added~3 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
    • Tools that change things, listed without credentials: 3 to 4

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http wall https://cellionaire.com/mcp
claude mcp add --transport http wall https://cellionaire.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wall__get_wall_info",
      "mcp__wall__read_region",
      "mcp__wall__get_order_status"
    ],
    "ask": [
      "mcp__wall__wall_overview",
      "mcp__wall__check_cells_available",
      "mcp__wall__prepare_x402_order",
      "mcp__wall__create_order"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wall. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.cellionaire/wall/verify?hash=0eb1fcc23573e4a375e59f4d55b9dd7ee1c62f92848bcd8cccf3bd8ea63cc686" | jq -e '.changed == false'

Pinned hash 0eb1fcc23573, from Nov 18, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.cellionaire/wall/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.cellionaire/wall
[![Anlyon Radar](https://radar.anlyon.com/badge/com.cellionaire/wall.svg)](https://radar.anlyon.com/servers/com.cellionaire/wall)

Source: MCP Registry. Synced Nov 4, 2026, 20:17 UTC.

Cellionaire MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Cellionaire MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Cellionaire MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Cellionaire MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Cellionaire MCP server have?

7 tools: 4 write, 3 read. wall_overview, check_cells_available, prepare_x402_order, create_order, get_wall_info, read_region and get_order_status.

Does the Cellionaire MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Cellionaire MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Cellionaire MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.