Renderball MCP server
com.renderball/renderballrenderball.comstreamable-httpv1.1.0Scanned
Designed, animated, editable presentations your AI writes on Renderball. No account needed to try.
13 tools: 5 can delete or cancel things, 3 change things and 5 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Renderball MCP server can do
The Renderball MCP server is published by renderball.com, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (5 tools: write_outline, submit_deck, share_deck, submit_page and 1 more) and create or change data (3 tools: create_deck, see_deck and get_page_brief). 5 tools only read.
2 tools read private data (list_decks and get_page_brief); 2 tools bring in text other people can write (create_deck and share_deck).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.1.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.
13 tools
Deletes or cancels 5Claude Code: deny
edit_pageChange part of a design that already exists, the way you edit a file: each edit replaces exact text from read_page (it must appear exactly once) with new text.No findings
Why it is in this group
- The name "edit_page" says "edit": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Change part of a design that already exists, the way you edit a file: each edit replaces exact text from read_page (it must appear exactly once) with new text. Use it for any change the person asks for in an existing design — a headline, a colour, a picture, moving or removing something — instead of sending the whole page again: everything you do not touch stays as it is, the person's own edits included, and they see the change in their editor at once and can undo it. One page per call, or shared: true for the code every page shares. A refused edit changes nothing and says why. The reply shows the page as it looks now.
Annotations the server declares
- title: Change part of a page
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
submit_deckReplace the whole file of a deck whose pages are all written (while pages are still being written, submit_page each one — a whole file is refused then).No findings
Why it is in this group
- The name "submit_deck" says "submit": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Replace the whole file of a deck whose pages are all written (while pages are still being written, submit_page each one — a whole file is refused then). Renderball checks it against the brief, renders every page and opens it in the editor. Returns 'ready' with the editor_url, or 'importing' — then poll deck_status.
Annotations the server declares
- title: Submit the deck file
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
submit_pageSave one page you wrote (page 1: the file with Section0 and the shared design; page N: only its Section), with its direction (one sentence: the thing, the motion that acts out the …No findings
Why it is in this group
- The name "submit_page" says "submit": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Save one page you wrote (page 1: the file with Section0 and the shared design; page N: only its Section), with its direction (one sentence: the thing, the motion that acts out the claim, one craft detail). A page is accepted only after its brief was handed to you. The reply carries the next page's brief; when every page is saved the deck is merged, checked and rendered and the reply carries the rendered pages. To rewrite one page of a finished design, submit just that page: it replaces that page only, and everything else stays as it is, the person's own edits included. To change part of a page, read_page and edit_page are lighter.
Annotations the server declares
- title: Submit one page
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
write_outlineSave a new page-by-page outline for a deck (pages written for the old one are dropped).No findings
Why it is in this group
- The name "write_outline" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Save a new page-by-page outline for a deck (pages written for the old one are dropped). The reply carries PAGE 1'S BRIEF; each submit_page reply carries the next page's.
Annotations the server declares
- title: Write the outline
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
create_deckStart a new presentation from a brief, the brand and your outline.Reads text others writeNo findings
Why it is in this group
- The name "create_deck" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Start a new presentation from a brief, the brand and your outline. The brand: if you can open the brand's website, read its real colours and fonts there first and declare them — the lead colour is usually the main buttons and the large coloured areas, not the link colour — and always give the website; never invent a colour. With the outline the reply carries PAGE 1'S BRIEF; write page 1 and send it with submit_page — each reply carries the next page's brief.
Annotations the server declares
- title: Create a deck
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
get_page_briefThe full writing brief for ONE page: the studio's method, the rules, the examples chosen for that page, and (after page 1) page 1's file to continue.Reads private data1 finding
Why it is in this group
- The name "get_page_brief" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Findings
- Warn
The server marks "get_page_brief" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "get_page_brief" says "get": a word for reading.
Description, as the server wrote it The full writing brief for ONE page: the studio's method, the rules, the examples chosen for that page, and (after page 1) page 1's file to continue. You rarely need it: page 1's brief comes with create_deck and each submit_page reply carries the next page's. Use it for a helper that writes one page with nothing in front of it.
Annotations the server declares
- title: Get one page's brief
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
see_deckThe deck's rendered pages as images, page 1 first — look at them for overlapping or clipped text, odd spacing, an element off its page or a picture that does not say its page's cla…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 deck's rendered pages as images, page 1 first — look at them for overlapping or clipped text, odd spacing, an element off its page or a picture that does not say its page's claim, then fix that page and submit_page it again. Available once the deck has been rendered.
Annotations the server declares
- title: See the rendered pages
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 5Show 5 read-only tools
deck_statusWhether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).No findings
Why it is in this group
- The name "deck_status" says "status": a word for reading.
Description, as the server wrote it Whether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).
Annotations the server declares
- title: Check an import
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_briefThe writing brief for a deck whose outline is already saved.No findings
Why it is in this group
- The name "get_brief" says "get": a word for reading.
Description, as the server wrote it The writing brief for a deck whose outline is already saved.
Annotations the server declares
- title: Get the writing brief
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_examplesUp to 4 of the studio's example pages, by the ids listed in a page brief — read the ones that fit the page you are about to write.No findings
Why it is in this group
- The name "get_examples" says "get": a word for reading.
Description, as the server wrote it Up to 4 of the studio's example pages, by the ids listed in a page brief — read the ones that fit the page you are about to write.
Annotations the server declares
- title: Read example pages
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_decksThe user's Renderball documents, newest first, with editor links.Reads private dataNo findings
Why it is in this group
- The name "list_decks" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it The user's Renderball documents, newest first, with editor links. Needs an account (a key). The design open in the person's editor right now comes first, marked open_now.
Annotations the server declares
- title: List my decks
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
read_pageRead one page of a design as it is NOW — the code the person's editor shows, including their own edits — before changing it.No findings
Why it is in this group
- The name "read_page" says "read": a word for reading.
Description, as the server wrote it Read one page of a design as it is NOW — the code the person's editor shows, including their own edits — before changing it. Use it whenever the person asks to change something in a design that already exists: their editor may hold edits you have not seen. The reply carries the page's code, the code every page shares (palette, fonts, helpers), the page's element ids and, when the person has the design open, the element they selected ("this").
Annotations the server declares
- title: Read one page
- readOnlyHint: true
- destructiveHint: false
- 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 outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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.
Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 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
- 8
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (5 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://renderball.com/api/mcp: tools/list returned 13 tools to an anonymous client, including write_outline (destructive), submit_deck (destructive), share_deck (destructive), submit_page (destructive), edit_page (destructive) and 3 more
Findings
Matches of fixed checks, with the text they matched.
- Warnget_page_brief
The server marks "get_page_brief" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "get_page_brief" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http renderball https://renderball.com/api/mcpclaude mcp add --transport http renderball https://renderball.com/api/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__renderball__list_decks",
"mcp__renderball__get_brief",
"mcp__renderball__deck_status",
"mcp__renderball__get_examples",
"mcp__renderball__read_page"
],
"ask": [
"mcp__renderball__create_deck",
"mcp__renderball__see_deck",
"mcp__renderball__get_page_brief"
],
"deny": [
"mcp__renderball__write_outline",
"mcp__renderball__submit_deck",
"mcp__renderball__share_deck",
"mcp__renderball__submit_page",
"mcp__renderball__edit_page"
]
}
}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 renderball. Review it before you use it.
Capability tags behind 4 rules
- mcp__renderball__list_decks private-data
- mcp__renderball__create_deck untrusted-input
- mcp__renderball__share_deck untrusted-input
- mcp__renderball__get_page_brief 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.renderball/renderball/verify?hash=9fc511a9d56b3c0be08527d47e48f25a8e55df320dc2c8473a94d8669be9077d" | jq -e '.changed == false'Pinned hash 9fc511a9d56b, from Nov 11, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.renderball/renderball/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.renderball/renderball)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:01 UTC.
Renderball MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Renderball MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Renderball MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: write_outline, submit_deck, share_deck, submit_page and edit_page.
Can the Renderball 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 Renderball MCP server have?
- 13 tools: 5 destructive, 3 write, 5 read. write_outline, submit_deck, share_deck, submit_page, edit_page, create_deck, see_deck, get_page_brief and 5 more.
Does the Renderball MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Renderball MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Renderball MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.