# Canvas64 (remote · canvas64.com)

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

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `canvas64.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-canvas64-wall/api-mcp.md), [page](https://verifymcp.io/servers/com-canvas64-wall/api-mcp)

## Channel facts

- Endpoint: `https://canvas64.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 585 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Canvas64 MCP server?

Canvas64 is a hosted endpoint at https://canvas64.com/api/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.

### Claude

```bash
claude mcp add --transport http com-canvas64-wall 'https://canvas64.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-canvas64-wall": {
      "url": "https://canvas64.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-canvas64-wall": {
      "type": "http",
      "url": "https://canvas64.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-canvas64-wall]
url = "https://canvas64.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-canvas64-wall": {
      "type": "remote",
      "url": "https://canvas64.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-canvas64-wall --url 'https://canvas64.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-canvas64-wall:
    url: "https://canvas64.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-canvas64-wall": {
      "Transport": "http",
      "Url": "https://canvas64.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-canvas64-wall -t streamable-http -u 'https://canvas64.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-canvas64-wall": {
      "type": "http",
      "url": "https://canvas64.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 85, +1)

- [functional] Server version: 1.6.6 → 1.6.8

### 2026-11-18 (score 84, 0)

- [functional] Server version: 1.6.5 → 1.6.6

### 2026-11-16 (score 84, +1)

- [functional] Server version: 1.6.3 → 1.6.5

### 2026-11-14 (score 83, +1)

- [functional] Server version: 1.6.2 → 1.6.3

### 2026-11-12 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `get_wall` (~89 tokens)

Read the wall

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.

Input parameters:

- `filter` (string): Which cells; all by default.

### `get_cell` (~87 tokens)

Read one cell

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.

Input parameters:

- `cell` (string, required): The cell's address, such as D4.

### `quote` (~111 tokens)

Price a step

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.

Input parameters:

- `step` (integer, required): The purchase number; 1 is a claim of a free cell.
- `until` (integer): Optional: a later step, to sum the royalty earned up to it.

### `prepare_buy` (~156 tokens)

Prepare a purchase

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.

Input parameters:

- `cell` (string, required): The cell's address, such as D4.
- `wallet` (string): Optional: the buyer's wallet address, to check its USDC balance and allowance.

### `get_rules` (~49 tokens)

The rules

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-canvas64-wall/api-mcp#diagnostics

## Score history

- 2026-11-21: 86
- 2026-11-20: 85
- 2026-11-19: 85
- 2026-11-18: 84
- 2026-11-17: 84
- 2026-11-16: 84
- 2026-11-15: 83
- 2026-11-14: 83
- 2026-11-13: 82
- 2026-11-12: 82
- 2026-11-11: 81
- 2026-11-10: 81
- 2026-11-09: 80
- 2026-11-08: 80
- 2026-11-07: 79
- 2026-11-06: 79
- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73

## Common questions

### What is the Canvas64 MCP server?

Canvas64 is an MCP server listed in the public MCP registry as com.canvas64/wall. A wall of 64 ad cells on Base: owners, prices, royalties, and purchases your own wallet signs. This page covers its hosted endpoint (https://canvas64.com/api/mcp).

### Is the Canvas64 MCP server safe to use?

Canvas64 scores 86 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 Canvas64 MCP server expose?

Canvas64 exposes 5 tools: get_wall, get_cell, quote, prepare_buy, get_rules. Their descriptions and schemas cost roughly 492 tokens of context every time the server is loaded.

### Does the Canvas64 MCP server require authentication?

No. We connected to Canvas64 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Canvas64 MCP server still maintained?

Canvas64 is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Canvas64 MCP server?

VerifyMCP ran 13 checks on Canvas64, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://canvas64.com/api/mcp
- Website: https://canvas64.com/docs/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-canvas64-wall/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-canvas64-wall/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-canvas64-wall/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-canvas64-wall/api-mcp
