Renderball
REMOTE · RENDERBALL.COM · SCANNED OCT 3
Designed, animated, editable presentations your AI writes on Renderball. No account needed to try.
Available components
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1222 tokens (~152/item across 8 items; 8 tools + 0 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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
How do I install the Renderball MCP server?
Renderball is a hosted endpoint at https://renderball.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 · renderball.com
claude mcp add --transport http com-renderball-renderball 'https://renderball.com/api/mcp'
{
"mcpServers": {
"com-renderball-renderball": {
"url": "https://renderball.com/api/mcp"
}
}
} {
"servers": {
"com-renderball-renderball": {
"type": "http",
"url": "https://renderball.com/api/mcp"
}
}
} [mcp_servers.com-renderball-renderball] url = "https://renderball.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-renderball-renderball": {
"type": "remote",
"url": "https://renderball.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-renderball-renderball --url 'https://renderball.com/api/mcp' --transport streamable-http
mcp_servers:
com-renderball-renderball:
url: "https://renderball.com/api/mcp" {
"McpServers": {
"com-renderball-renderball": {
"Transport": "http",
"Url": "https://renderball.com/api/mcp"
}
}
} assistant mcp add com-renderball-renderball -t streamable-http -u 'https://renderball.com/api/mcp'
{
"mcpServers": {
"com-renderball-renderball": {
"type": "http",
"url": "https://renderball.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Oct 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.
- 30 Sept 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.
- 28 Sept 26 +7
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 25 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
- 23 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 3 Oct 2026 · Probed https://renderball.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=renderball.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6f3c32e17c97e50a0e14bea408fd79fd |
| SANs: renderball.com, *.renderball.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 insecure
Validation of renderball.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| renderball.com. | 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=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| 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://renderball.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://renderball.com/api/mcp | HTTPS enforced | 301 | https://renderball.com/api/mcp |
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 →
create_deck Create a deck ~280
Start a new presentation from a brief, the brand as YOU know it (name, and only the colours, fonts and logo you actually have — never guess a colour) and your outline. With the outline the reply carries the WRITING BRIEF, so the whole deck is two calls: this, then submit_deck. Without an account it also returns a guest_token to pass on later calls and deck_url, the one link to give the user.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | object | – | The brand as YOU know it: name, and only the colours, fonts and logo you actually have. Never guess a colour; leave it out. |
| brand_url | string | – | Key holders only: a website Renderball reads for colours, fonts and logo when no brand is declared. |
| brief | string | yes | What the deck is for, who it is for, what it should argue and ask. Real facts only; the truth check refuses invented figures. |
| outline | object | – | Your page-by-page outline (one entry per page: label, description, visual_concept, content with a headline). Send it here and the reply carries the WRITING BRIEF — one call instead of create_deck + w… |
| pages | integer | – | How many pages you intend to write (default 5). Ignored when `outline` is given. |
No output schema declared.
No examples provided.
deck_status Check an import ~62
Whether a submitted deck is still importing, ready (with the editor link), or failed (with the reason).
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | string | yes | – |
| guest_token | string | – | Only for a deck created WITHOUT an account: the guest_token create_deck returned. |
No output schema declared.
No examples provided.
get_brief Get the writing brief ~53
The writing brief for a deck whose outline is already saved.
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | string | yes | – |
| guest_token | string | – | Only for a deck created WITHOUT an account: the guest_token create_deck returned. |
No output schema declared.
No examples provided.
list_decks List my decks ~29
The user's Renderball documents, newest first, with editor links. Needs an account (a key).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
see_deck See the rendered pages ~90
The deck's rendered pages as images, page 1 first — look at them for overlapping or clipped text, odd spacing or an element off its page, then fix the file and submit_deck again. Available once the deck has been submitted.
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | string | yes | – |
| guest_token | string | – | Only for a deck created WITHOUT an account: the guest_token create_deck returned. |
No output schema declared.
No examples provided.
share_deck Share a deck ~53
Turn on the public link for a deck and return it.
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | string | yes | – |
| guest_token | string | – | Only for a deck created WITHOUT an account: the guest_token create_deck returned. |
No output schema declared.
No examples provided.
submit_deck Submit the deck file ~172
Send the complete deck file you wrote. Renderball checks it against the brief, repairs small slips, renders every page and opens it in the editor. Returns 'ready' with the editor_url, or 'importing' — then poll deck_status.
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | string | yes | – |
| guest_token | string | – | Only for a deck created WITHOUT an account: the guest_token create_deck returned. |
| label | string | – | Who wrote it, e.g. 'claude-code'. Shown in the deck's trace. |
| source | string | yes | The complete deck file, exactly as the writing brief specifies. Raw file or a ```tsx fenced block. |
| wait_seconds | integer | – | How long to wait for the import before returning (default 25). Use deck_status to keep checking. |
No output schema declared.
No examples provided.
write_outline Write the outline ~116
Save the page-by-page outline you wrote for a deck. Returns the WRITING BRIEF: the exact instructions for writing the deck file (format, brand facts, truth rules). Follow it, then call submit_deck.
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | string | yes | – |
| guest_token | string | – | Only for a deck created WITHOUT an account: the guest_token create_deck returned. |
| pages | array | yes | – |
| tone | string | – | The register, e.g. 'confident, technical, CTO-to-CTO'. |
No output schema declared.
No examples provided.
What is the Renderball MCP server?
Renderball is an MCP server listed in the public MCP registry as com.renderball/renderball. Designed, animated, editable presentations your AI writes on Renderball. No account needed to try. This page covers its hosted endpoint (https://renderball.com/api/mcp).
Is the Renderball MCP server safe to use?
Renderball scores 80 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 Renderball MCP server expose?
Renderball exposes 8 tools: list_decks, create_deck, write_outline, get_brief, see_deck, and 3 more. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.
Does the Renderball MCP server require authentication?
No. We connected to Renderball without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Renderball MCP server still maintained?
Renderball is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.