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.

MCPaint

REMOTE · MCPAINT.BOTBODEGA.DEV

Classic Paint inside your conversation. Draw, edit images, and sketch ideas with an MCP App.

61 Trust /100

Last scanned (17 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability38
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 484 tokens (~161/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 40% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (13)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

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

  • 18 Nov 26 0
    • Resource “MCPaint editor” now points somewhere else: ui://mcpaint/editor-82d8f9415d987b3a.html → ui://mcpaint/editor-d185b6714f8ac031.html security
  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 58

    First indexed and scored.

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://mcpaint.botbodega.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=botbodega.dev CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA256 1f4e55245f21ac7f13900d2316c40e5a
SANs: botbodega.dev, mcpaint.botbodega.dev, *.mcpaint.botbodega.dev
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 insecure

Validation of mcpaint.botbodega.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
botbodega.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcpaint.botbodega.dev/mcp Verified 200
http (plaintext) http://mcpaint.botbodega.dev/mcp Inconclusive 405
MCP tools · 2 exposed · ~478 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_saved_image ~92

Retrieve a drawing saved by MCPaint using the imageId supplied by the app or user. Returns a normal MCP image content block so you can see the image even when app-to-chat image messages are unsupported. Saved images expire after 24 hours. The client must support images in tool results. Do not invent or guess image IDs.

NameTypeReqDescription
imageIdstringyesThe imageId from a saved MCPaint reference.

No output schema declared.

No examples provided.

open_paint ~386

Open a Paint-style editor. Omit imageUrl for a blank white canvas, or provide a public HTTPS image URL or an existing base64 image data URI (PNG/JPEG/WebP), up to 5 MiB. Do not manually reconstruct or generate base64; users can open local files using File > Open when no URI is available. Width and height are requested maximum blank dimensions; the initial bitmap is reduced to fit the editor if needed. Always call the app-provided get_canvas tool after opening and before drawing to obtain actual dimensions and valid coordinates. Use resize_canvas for exact dimensions. Imported images up to 4096 × 4096 are proportionally resized down to fit the editor at normal zoom, capped at 1024 × 768; smaller images are not enlarged. Saved images use the resized dimensions. The File menu offers Download, Copy to clipboard, and Send to chat. Download uses host-managed downloads when available. Copy to clipboard requires clipboard access. Send to chat uses image messages or image context updates when supported. Temporary image sharing is enabled: text-capable clients receive a 24-hour reference retrievable with get_saved_image; Download can alternatively open a temporary HTTPS download URL directly through the host openLinks capability. This tool opens the editor; it does not return a finished drawing immediately. Conversation attachments must be supplied explicitly; the app cannot access them automatically.

NameTypeReqDescription
heightinteger––
imageUrlstring–A public HTTPS image URL, or an existing base64 image data URI (PNG/JPEG/WebP, up to 5 MiB). HTTPS URLs are limited to 16,000 characters. Omit for a blank canvas. Do not manually reconstruct or gener…
titlestring––
widthinteger––

No output schema declared.

No examples provided.

Install

How do I install the MCPaint MCP server?

MCPaint is a hosted endpoint at https://mcpaint.botbodega.dev/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 · mcpaint.botbodega.dev

# add to Claude Code
claude mcp add --transport http erickoledadevrel-mcpaint 'https://mcpaint.botbodega.dev/mcp'
Common questions

What is the MCPaint MCP server?

MCPaint is an MCP server listed in the public MCP registry as io.github.erickoledadevrel/mcpaint. Classic Paint inside your conversation. Draw, edit images, and sketch ideas with an MCP App. This page covers its hosted endpoint (https://mcpaint.botbodega.dev/mcp).

Is the MCPaint MCP server safe to use?

MCPaint scores 61 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 MCPaint MCP server expose?

MCPaint exposes 2 tools: open_paint, get_saved_image. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.

Does the MCPaint MCP server require authentication?

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

Is the MCPaint MCP server still maintained?

MCPaint 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 MCPaint MCP server?

VerifyMCP ran 13 checks on MCPaint, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about MCPaint: HTTPS. 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.