# Renderball (remote · renderball.com)

Designed, animated, editable presentations your AI writes on Renderball. No account needed to try.

- Trust score: 80/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `renderball.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-renderball-renderball/api-mcp.md), [page](https://verifymcp.io/servers/com-renderball-renderball/api-mcp)

## Channel facts

- Endpoint: `https://renderball.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 68% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-renderball-renderball 'https://renderball.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-renderball-renderball": {
      "url": "https://renderball.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-renderball-renderball": {
      "type": "http",
      "url": "https://renderball.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-renderball-renderball]
url = "https://renderball.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-renderball-renderball": {
      "type": "remote",
      "url": "https://renderball.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-renderball-renderball --url 'https://renderball.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-renderball-renderball:
    url: "https://renderball.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-renderball-renderball": {
      "Transport": "http",
      "Url": "https://renderball.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-renderball-renderball -t streamable-http -u 'https://renderball.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 80, +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.

### 2026-09-30 (score 79, +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.

### 2026-09-28 (score 78, +7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71, +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.

### 2026-09-25 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-21 (score 68, +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.

### 2026-09-19 (score 67, +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.

## MCP tools (8)

### `list_decks` (~29 tokens)

List my decks

The user's Renderball documents, newest first, with editor links. Needs an account (a key).

### `create_deck` (~280 tokens)

Create a deck

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.

Input parameters:

- `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, required): 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.

### `write_outline` (~116 tokens)

Write the outline

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.

Input parameters:

- `deck_id` (string, required)
- `guest_token` (string): Only for a deck created WITHOUT an account: the guest_token create_deck returned.
- `pages` (array, required)
- `tone` (string): The register, e.g. 'confident, technical, CTO-to-CTO'.

### `get_brief` (~53 tokens)

Get the writing brief

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

Input parameters:

- `deck_id` (string, required)
- `guest_token` (string): Only for a deck created WITHOUT an account: the guest_token create_deck returned.

### `see_deck` (~90 tokens)

See the rendered pages

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.

Input parameters:

- `deck_id` (string, required)
- `guest_token` (string): Only for a deck created WITHOUT an account: the guest_token create_deck returned.

### `submit_deck` (~172 tokens)

Submit the deck file

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.

Input parameters:

- `deck_id` (string, required)
- `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, required): 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.

### `deck_status` (~62 tokens)

Check an import

Whether a submitted deck is still importing, ready (with the editor link), or failed (with the reason).

Input parameters:

- `deck_id` (string, required)
- `guest_token` (string): Only for a deck created WITHOUT an account: the guest_token create_deck returned.

### `share_deck` (~53 tokens)

Share a deck

Turn on the public link for a deck and return it.

Input parameters:

- `deck_id` (string, required)
- `guest_token` (string): Only for a deck created WITHOUT an account: the guest_token create_deck returned.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-renderball-renderball/api-mcp#diagnostics

## Score history

- 2026-10-03: 80
- 2026-10-02: 80
- 2026-10-01: 79
- 2026-09-30: 79
- 2026-09-29: 78
- 2026-09-28: 78
- 2026-09-27: 71
- 2026-09-26: 70
- 2026-09-25: 70
- 2026-09-24: 69
- 2026-09-23: 69
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65
- 2026-09-15: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://renderball.com/api/mcp
- Repository: https://github.com/agarces1999/renderball-skills
- Website: https://renderball.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-renderball-renderball/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-renderball-renderball/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-renderball-renderball/api-mcp