# RIFFCADE (remote · mcp.riffcade.com)

Free, ad-free open-source browser games that open and play right inside the chat.

- Trust score: 18/100 (low)
- Change this week: −55
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

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

## Channel facts

- Endpoint: `https://mcp.riffcade.com/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-11-06.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 530.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the RIFFCADE MCP server?

RIFFCADE is a hosted endpoint at https://mcp.riffcade.com/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-riffcade-arcade 'https://mcp.riffcade.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-riffcade-arcade": {
      "url": "https://mcp.riffcade.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-riffcade-arcade]
url = "https://mcp.riffcade.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-riffcade-arcade:
    url: "https://mcp.riffcade.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-riffcade-arcade": {
      "type": "http",
      "url": "https://mcp.riffcade.com/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-11-06 (score 18, 0)

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

### 2026-11-03 (score 18, −56)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.67 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 74, +1)

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

### 2026-10-30 (score 73, +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-10-28 (score 72, +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-10-25 (score 71, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “new_games” rewrote its description, which is the text the model reads
- [security] Tool “play_game” rewrote its description, which is the text the model reads
- [security] Tool “rate_game” rewrote its description, which is the text the model reads
- [security] Tool “show_arcade” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 63 → 52
- [cosmetic] “rate_game” dropped the optional parameter “client”

### 2026-10-23 (score 70, −4)

- [security regression] HTTPS: pass → unverified

### 2026-10-22 (score 74, +1)

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

## MCP tools (4)

### `show_arcade` (~99 tokens)

Show the arcade

Show AGENTPARK: free open-source browser games that play well on a phone. Use when the user asks for AGENTPARK, the arcade, or a game to play or browse. Optional category filter (Puzzle, Arcade, Action, Racing, Strategy, Idle, Word & Math, 3D, Retro, 2-Player) or a search word.

Input parameters:

- `category` (string)
- `query` (string)

### `new_games` (~27 tokens)

Today's new games

Show the games added to AGENTPARK most recently (new games arrive twice a day).

### `play_game` (~49 tokens)

Play a game

Open one AGENTPARK game ready to play, by its name or slug.

Input parameters:

- `game` (string, required): Game name or slug, e.g. "Snake Pro" or "skifree"

### `rate_game` (~48 tokens)

Rate a game

Record the user's 1-5 star rating for an AGENTPARK game. Only call when the user gives a rating.

Input parameters:

- `slug` (string, required)
- `stars` (integer, required)

## Diagnostics

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

## Score history

- 2026-11-06: 18
- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 69

## Common questions

### What is the RIFFCADE MCP server?

RIFFCADE is an MCP server listed in the public MCP registry as com.riffcade/arcade. Free, ad-free open-source browser games that open and play right inside the chat. This page covers its hosted endpoint (https://mcp.riffcade.com/mcp).

### Is the RIFFCADE MCP server safe to use?

RIFFCADE scores 18 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 RIFFCADE MCP server expose?

RIFFCADE exposes 4 tools: show_arcade, new_games, play_game, rate_game. Their descriptions and schemas cost roughly 223 tokens of context every time the server is loaded.

### Does the RIFFCADE MCP server require authentication?

Its publisher declares no required credentials for RIFFCADE. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the RIFFCADE MCP server still maintained?

RIFFCADE is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the RIFFCADE MCP server?

VerifyMCP ran 4 checks on RIFFCADE, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about RIFFCADE: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.riffcade.com/mcp
- Website: https://riffcade.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-riffcade-arcade/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-riffcade-arcade/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-riffcade-arcade/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-riffcade-arcade/mcp