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.

Canvas64

REMOTE · CANVAS64.COM

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

Available components

+3 this week 86 Trust /100

Last scanned (16 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 585 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +1
    • Server version: 1.6.6 → 1.6.8 functional
  • 18 Nov 26 0
    • Server version: 1.6.5 → 1.6.6 functional
  • 16 Nov 26 +1
    • Server version: 1.6.3 → 1.6.5 functional
  • 14 Nov 26 +1
    • Server version: 1.6.2 → 1.6.3 functional
  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 26 +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.

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 21 Nov 2026 · Probed https://canvas64.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=canvas64.com CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 e0c5dc4458ce379213ac5e5fddd08bab
SANs: canvas64.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of canvas64.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
canvas64.com. DS published 2371 13 Verified
canvas64.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://canvas64.com/api/mcp Verified 200
http (plaintext) http://canvas64.com/api/mcp HTTPS enforced 301 https://canvas64.com/api/mcp
MCP tools · 5 exposed · ~492 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
get_cell ~87

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.

NameTypeReqDescription
cellstringyesThe cell's address, such as D4.

No output schema declared.

No examples provided.

get_rules ~49

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_wall ~89

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.

NameTypeReqDescription
filterstring–Which cells; all by default.

No output schema declared.

No examples provided.

prepare_buy ~156

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.

NameTypeReqDescription
cellstringyesThe cell's address, such as D4.
walletstring–Optional: the buyer's wallet address, to check its USDC balance and allowance.

No output schema declared.

No examples provided.

quote ~111

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.

NameTypeReqDescription
stepintegeryesThe purchase number; 1 is a claim of a free cell.
untilinteger–Optional: a later step, to sum the royalty earned up to it.

No output schema declared.

No examples provided.

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.

remote · canvas64.com

# add to Claude Code
claude mcp add --transport http com-canvas64-wall 'https://canvas64.com/api/mcp'
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.