Renderball MCP server

• Registry namecom.renderball/renderballverified in the MCP registry

The registry name sits under renderball.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-25
• Tools13
• Server calls itselfrenderball
• Server version1.3.0
• Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 121 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score75 of 100answers 100 · definitions 86 · context 91 · connects 100 · lowered by the warning signs below
• Answered100% of days10 of 10 daily checks
• Median first answer181 ms
• Space in an agent's context≈ 4,216 tokensthe definitions of all its tools (13), which an agent carries on every turn
• Tool definitionsB · 86 of 100
• Typed results0 of 13 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 11 of 13

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_decks

  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.

• create_deck

  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…

• write_outline

  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.

• get_brief

  The writing brief for a deck whose outline is already saved.

• see_deck

  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…

• submit_deck

  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…

• deck_status

  Whether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).

• share_deck

  Turn on the public link for a deck and return it: anyone with the link can view the deck.

• get_page_brief

  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…

• get_examples

  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.

• submit_page

  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…

• read_page

  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…

• edit_page

  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…