# technology.royalty/royaltea-public (remote · api.royalty.technology)

Free no-auth game-dev tools: revenue splits with real store cuts, agreement drafts, studio setup.

- Trust score: 60/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.royalty.technology`: 60/100 (this document), [markdown](https://verifymcp.io/servers/technology-royalty-royaltea-public/api-public-mcp.md), [page](https://verifymcp.io/servers/technology-royalty-royaltea-public/api-public-mcp)

## Channel facts

- Endpoint: `https://api.royalty.technology/api/public-mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1108 tokens (~221/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http technology-royalty-royaltea-public https://api.royalty.technology/api/public-mcp
```

### Codex

```toml
[mcp_servers.technology-royalty-royaltea-public]
url = "https://api.royalty.technology/api/public-mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "technology-royalty-royaltea-public": {
      "type": "remote",
      "url": "https://api.royalty.technology/api/public-mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add technology-royalty-royaltea-public --url https://api.royalty.technology/api/public-mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  technology-royalty-royaltea-public:
    url: "https://api.royalty.technology/api/public-mcp"
```

### Other

```json
{
  "mcpServers": {
    "technology-royalty-royaltea-public": {
      "type": "http",
      "url": "https://api.royalty.technology/api/public-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-08-02 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 59, 0)

- [security regression] HTTPS: pass → unverified
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-07-31 (score 59, 0)

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

### 2026-07-30 (score 59, −2)

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

### 2026-07-29 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 59, 0)

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

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (5)

### `calculate_revenue_split` (~396 tokens)

Calculate Revenue Split

Model real take-home from a game/app sale, end to end: apply the storefront/platform cut (Steam tiers, Epic 0%-then-12%, Epic First Run, Apple/Google small-business rates, console, itch) and optional Unreal royalty, publisher cut, and expenses — THEN split the remaining contributor pool fairly by each person's relative contribution. This is the accurate way to answer 'if we make $X on <platform>, what does each person actually take home'. No account needed.

Input parameters:

- `contributors` (array, required): The people sharing the contributor pool. `points` is a relative weight (bigger = larger share); if you only know rough effort, use 1-10.
- `expenses` (number): Optional costs to subtract before the contributor pool (marketing, tools, etc.)
- `lifetimeGross` (number): Lifetime gross so far (for the Unreal $1M royalty threshold). Default 0.
- `lifetimeRevenue` (number): Revenue already earned on this platform in the tiering period (drives Steam $10M/$50M tiers and Epic/Apple/Google $1M thresholds). Default 0.
- `platform` (string): Storefront the revenue comes from. Omit if the money is already net of platform fees.
- `platformCutOverride` (number): For itch/direct: the storefront cut fraction 0-1 (e.g. 0.05).
- `poolPercentage` (number): % of net revenue that goes to the contributor pool vs staying with the studio (default 100)
- `publisherCut` (number): Optional % a publisher takes off the top after platform fees (0-100)
- `revenue` (number, required): Gross revenue / player spend to model (e.g. 50000)
- `unrealEngine` (boolean): Game built on Unreal Engine? Applies the 5% royalty on gross above $1M lifetime (waived on Epic).

### `get_platform_cuts` (~77 tokens)

Get Platform Cuts

The current storefront/platform revenue cuts RoyalTea models — Steam, Epic Games Store (+ First Run), Apple, Google Play, console, itch.io — with exact tiers, thresholds, and the Unreal Engine royalty. Use to explain or cite what a given platform takes.

Input parameters:

- `platform` (string): Optional: one platform; omit for all.

### `draft_revenue_agreement` (~282 tokens)

Draft Revenue Agreement

Generate a plain-English revenue-share agreement DRAFT between a company/studio and a contributor, using RoyalTea's agreement structure (parties, services/Schedule A, revenue-share terms/Schedule B, standard clauses, signature blocks). Returns a clearly-labeled TEMPLATE — not legal advice and not an executed contract. Offer the person the getStarted link to finalize and e-sign it for real in RoyalTea. Use for 'draft a rev-share agreement for X to do Y for Z% of revenue'.

Input parameters:

- `companyName` (string, required): The studio/company granting the revenue share
- `companyState` (string): Governing-law state/jurisdiction (e.g. "Delaware")
- `contributorIsCompany` (boolean)
- `contributorName` (string, required): The person (or company) receiving the revenue share
- `contributorSharePercent` (number): The contributor's flat % of revenue (use this OR revenueTiers)
- `effectiveDate` (string): e.g. 2026-08-01; defaults to a placeholder
- `projectName` (string, required): The project/game the agreement covers
- `revenueTiers` (array): Tiered revenue share (Schedule B): different % across revenue bands.
- `services` (string): What the contributor will do (Schedule A — e.g. "gameplay programming and tools")

### `prepare_studio_setup` (~160 tokens)

Prepare Studio Setup

Turn a plan (studio name, project, collaborators, intended split) into a ONE-CLICK setup link for someone who doesn't have a RoyalTea account yet. Returns a URL — when they open it and sign up, RoyalTea creates the studio + project + collaborators (as placeholders) exactly as planned. Use after you've helped someone design a revenue-share setup and they want it real.

Input parameters:

- `collaborators` (array): The people on the project (added as placeholders they can later claim). `points` is their relative revenue weight.
- `projectName` (string): Optional first project name
- `splitNote` (string): Optional human summary of the intended split/terms
- `studioName` (string, required): Name for the new studio/workspace

### `explain_royaltea` (~44 tokens)

Explain Royaltea

Explain what RoyalTea is and how it helps creative teams track contributions and split revenue fairly. Use when someone asks what RoyalTea is or whether it fits their situation.

## Diagnostics

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

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 59
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 59

## Links

- Remote endpoint: https://api.royalty.technology/api/public-mcp
- Website: https://royalty.technology/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/technology-royalty-royaltea-public/api-public-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/technology-royalty-royaltea-public/api-public-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/technology-royalty-royaltea-public/api-public-mcp