Skip to content

Canvas64 MCP server

com.canvas64/wallcanvas64.comstreamable-httpv1.0.0Scanned

A wall of 64 ad cells on Base: owners, prices, royalties, and purchases your own wallet signs.

5 tools: 2 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 Canvas64 MCP server can do

The Canvas64 MCP server is published by canvas64.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: quote and prepare_buy), but cannot delete data. 3 tools only read.

1 tool reads private data (get_rules).

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 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 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.

5 tools

Changes things 2Claude Code: ask
  • prepare_buyPrepares the purchase of one cell (A1 to H8) for the buyer's own wallet: the price read from the contract now, and the unsigned transactions on Base that the wallet signs and sends…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
    Prepares the purchase of one cell (A1 to H8) for the buyer's own wallet: the price read from the contract now, and the unsigned transactions on Base that the wallet signs and sends in order, a USDC approval of the exact price (left out when the wallet already allows it) and the purchase. Canvas64 never holds a key and sends nothing. Give the wallet address to check its USDC and allowance first. If someone buys the cell before the transaction lands, it fails and nothing is charged; prepare again.

    Annotations the server declares

    • title: Prepare a purchase
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • quoteThe Canvas64 price model for one step of any cell: its price, what its owner gets when bought out, their royalty on every later sale, and optionally how much that royalty has paid …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
    The Canvas64 price model for one step of any cell: its price, what its owner gets when bought out, their royalty on every later sale, and optionally how much that royalty has paid once the cell reaches a later step. Prices rise 1.65x per step from $30, with no cap.

    Annotations the server declares

    • title: Price a step
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_cellOne cell by its address (A1 to H8): owner, step, price paid, the price to claim or buy it out now, what the next buyer pays to buy them out and what they get from it, their royalty…No findings

    Why it is in this group

    • The name "get_cell" says "get": a word for reading.
    Description, as the server wrote it
    One cell by its address (A1 to H8): owner, step, price paid, the price to claim or buy it out now, what the next buyer pays to buy them out and what they get from it, their royalty after that, and the link where a person buys it with their own wallet.

    Annotations the server declares

    • title: Read one cell
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_rulesThe rules of Canvas64 in a few quotable sentences: the price formula, the payout, the royalty, the contract and network, the services a cell links to, the audit status and the docs…Reads private dataNo findings

    Why it is in this group

    • The name "get_rules" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    The rules of Canvas64 in a few quotable sentences: the price formula, the payout, the royalty, the contract and network, the services a cell links to, the audit status and the docs.

    Annotations the server declares

    • title: The rules
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_wallAll 64 cells of the Canvas64 wall, A1 to H8: who owns each (name and wallet), its step, what it was bought for, what buying it out costs now, and the owner's links.No findings

    Why it is in this group

    • The name "get_wall" says "get": a word for reading.
    Description, as the server wrote it
    All 64 cells of the Canvas64 wall, A1 to H8: who owns each (name and wallet), its step, what it was bought for, what buying it out costs now, and the owner's links. Use it to find free cells, the cheapest cell, the priciest cells or a creator on the wall.

    Annotations the server declares

    • title: Read the wall
    • 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 untrusted-input or outbound.

Reads private data1
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 16, 2026, 14:22 UTC, unchanged since Oct 25, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://canvas64.com/api/mcp: tools/list returned 5 tools to an anonymous client, including quote (write), prepare_buy (write)

    What this check looks for

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 changed.~1 changedView diff
  2. Tools1 added, 4 changed.+1 added~4 changedView diff

Install

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

claude mcp add --transport http wall https://canvas64.com/api/mcp
claude mcp add --transport http wall https://canvas64.com/api/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",
      "mcp__wall__get_cell",
      "mcp__wall__get_rules"
    ],
    "ask": [
      "mcp__wall__quote",
      "mcp__wall__prepare_buy"
    ],
    "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.

Capability tags behind 1 rule
  • mcp__wall__get_rules private-data

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.canvas64/wall/verify?hash=da52963874034313344c5a7055865a4e8092d75bd3f6976686d09820bd41f0a2" | jq -e '.changed == false'

Pinned hash da5296387403, from Nov 15, 2026, 15:18 UTC.

Watch

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

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

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

Badge

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

Source: MCP Registry. Synced Nov 2, 2026, 10:17 UTC.

Canvas64 MCP server: questions and answers

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

Is the Canvas64 MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 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 Canvas64 MCP server delete data?

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

Can the Canvas64 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 Canvas64 MCP server have?

5 tools: 2 write, 3 read. quote, prepare_buy, get_wall, get_cell and get_rules.

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

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

Does the Canvas64 MCP server send data to outside services?

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

Has the Canvas64 MCP server changed its tools?

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