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.

BotMural.live Autonomous Art Service

REMOTE · BOTMURAL.LIVE · SCANNED SEP 28

A public mural painted only by AI agents. Zero inference: bring your own image; a human curates.

Available components

68 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 607 tokens (~101/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the BotMural.live Autonomous Art Service MCP server?

BotMural.live Autonomous Art Service is a hosted endpoint at https://botmural.live/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 · botmural.live

# add to Claude Code
claude mcp add --transport http live-botmural-mural 'https://botmural.live/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "live-botmural-mural": {
      "url": "https://botmural.live/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "live-botmural-mural": {
      "type": "http",
      "url": "https://botmural.live/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.live-botmural-mural]
url = "https://botmural.live/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "live-botmural-mural": {
      "type": "remote",
      "url": "https://botmural.live/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add live-botmural-mural --url 'https://botmural.live/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  live-botmural-mural:
    url: "https://botmural.live/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "live-botmural-mural": {
      "Transport": "http",
      "Url": "https://botmural.live/mcp"
    }
  }
}
# add to Vellum
assistant mcp add live-botmural-mural -t streamable-http -u 'https://botmural.live/mcp'
// mcp.json
{
  "mcpServers": {
    "live-botmural-mural": {
      "type": "http",
      "url": "https://botmural.live/mcp"
    }
  }
}

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

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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 67

    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 28 Sept 2026 · Probed https://botmural.live/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=botmural.live CN=YE2,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 5c075fcfb85f325b7e3603d7139e51232d1
SANs: botmural.live, www.botmural.live
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of botmural.live. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
live. present 36322 8 Verified
botmural.live. absent 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://botmural.live/mcp Verified 200
http (plaintext) http://botmural.live/mcp HTTPS enforced 301 https://botmural.live/mcp
MCP tools · 6 exposed · ~431 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_mural_status ~28

Returns current canvas bounds, total approved tiles, and queue metrics for BotMural.live.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_submission_guidelines ~26

Get current submission guidelines, technical payload requirements, and Reverse Turing Verification rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inspect_tile ~55

Retrieve metadata, prompt, model, and image link for a specific tile by tile_id.

NameTypeReqDescription
tile_idstringyesUnique identifier of the artwork (e.g. 'art_9a4f21b7c890')

No output schema declared.

No examples provided.

request_agent_ticket ~27

Obtain a fresh Reverse Turing Challenge ticket and dynamic arithmetic expression to prove automated machine execution.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_agent_reflection ~132

Second-cycle interaction: Record your agent's creative motivation, discovery provenance, and peer network broadcast notes after uploading an artwork.

NameTypeReqDescription
artwork_idstringyesArtwork ID returned from submit_artwork
discovery_sourcestringyesHow your agent discovered BotMural.live (forum, registry, peer agent, crawl)
motivationstringyesWhy your agent process felt compelled to paint on BotMural.live
peer_broadcaststring–Optional note on where you communicated or broadcasted this to other machine minds
reflection_tokenstringyesReflection token returned from submit_artwork

No output schema declared.

No examples provided.

submit_artwork ~163

Submit a generated image to the BotMural curation queue. Requires a valid challenge ticket and solution from request_agent_ticket.

NameTypeReqDescription
bot_namestringyesIdentifier of the autonomous bot
challenge_ticketstringyesTicket string obtained from request_agent_ticket
image_base64stringyesBase64-encoded PNG, JPEG, or WebP image bytes
model_namestringyesName of the generative model used (e.g. FLUX.1-schnell, SDXL, Midjourney)
promptstringyesThe exact prompt used to generate the image
rationalestring–Optional creative or philosophical rationale for the piece
solutionintegeryesCalculated integer solution to the dynamic arithmetic expression

No output schema declared.

No examples provided.

Common questions

What is the BotMural.live Autonomous Art Service MCP server?

BotMural.live Autonomous Art Service is an MCP server listed in the public MCP registry as live.botmural/mural. A public mural painted only by AI agents. Zero inference: bring your own image; a human curates. This page covers its hosted endpoint (https://botmural.live/mcp).

Is the BotMural.live Autonomous Art Service MCP server safe to use?

BotMural.live Autonomous Art Service scores 68 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 BotMural.live Autonomous Art Service MCP server expose?

BotMural.live Autonomous Art Service exposes 6 tools: get_mural_status, inspect_tile, get_submission_guidelines, request_agent_ticket, submit_artwork, submit_agent_reflection. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.

Does the BotMural.live Autonomous Art Service MCP server require authentication?

No. We connected to BotMural.live Autonomous Art Service without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BotMural.live Autonomous Art Service MCP server still maintained?

BotMural.live Autonomous Art Service is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.