# Playtable (remote · play.rowhousesoftware.com)

Make up any game and play it in chat: a fair table that deals, hides cards and rolls dice.

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-12). See the changelog below before you install this server.

## Components

- remote · `play.rowhousesoftware.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-rowhousesoftware-playtable/play.md), [page](https://verifymcp.io/servers/com-rowhousesoftware-playtable/play)

## Channel facts

- Endpoint: `https://play.rowhousesoftware.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-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_game).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1251 tokens (~208/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% 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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

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

Playtable is a hosted endpoint at https://play.rowhousesoftware.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-rowhousesoftware-playtable 'https://play.rowhousesoftware.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-rowhousesoftware-playtable": {
      "url": "https://play.rowhousesoftware.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-rowhousesoftware-playtable": {
      "type": "http",
      "url": "https://play.rowhousesoftware.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-rowhousesoftware-playtable]
url = "https://play.rowhousesoftware.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-rowhousesoftware-playtable --url 'https://play.rowhousesoftware.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rowhousesoftware-playtable:
    url: "https://play.rowhousesoftware.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rowhousesoftware-playtable": {
      "Transport": "http",
      "Url": "https://play.rowhousesoftware.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rowhousesoftware-playtable -t streamable-http -u 'https://play.rowhousesoftware.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-rowhousesoftware-playtable": {
      "type": "http",
      "url": "https://play.rowhousesoftware.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-20 (score 63, +1)

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

### 2026-11-18 (score 62, +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.

### 2026-11-16 (score 61, +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-11-14 (score 60, +1)

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

### 2026-11-12 (score 59, −6)

- [critical regression] Authorization: partial → fail
- [security] New tool “delete_game”, which the server declares destructive
- [functional regression] Schema quality: 1131 → 1251
- [functional] Destructive annotations: pass → 100

### 2026-11-10 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 64)

First indexed and scored.

## MCP tools (5)

### `create_game` (~439 tokens)

Create a game

Set up any game to play in this chat: board games, card games, dice games, word and guessing games, mysteries. Describe it with the building blocks below, or pass starter for a ready one (tic-tac-toe, four-in-a-row, gomoku, checkers, reversi, crazy-eights, go-fish, twenty-one, pig, sea-battle, hangman, twenty-questions). The server keeps the board, deals and hides cards, rolls dice and enforces turns, so the player can trust the game. The player gets an interactive board in the chat (and a link to play in a browser or invite friends). Returns game_id and agent_key; keep both for get_state and take_turn. You run the rules that aren't built in.

Input parameters:

- `about` (string): The rules in a few sentences, shown to the player. Write them so you can follow them too.
- `board` (object)
- `counters` (array): Scores and tallies: "score", or {name, per_seat: false, start}.
- `deal` (integer): Cards dealt to each hand at the start.
- `deck`: "standard" (52, ids like AS, 10H, QC), "standard_jokers", "numbers:1-10x4", or a list of card labels or {label, suit, rank}. Adds a face-down deck, a face-up table and a hidden hand per seat.
- `dice` (integer): Default die sides.
- `first` (string): Seat name that goes first.
- `pieces` (array): Starting pieces.
- `piles` (array)
- `rules` (object): Rules the server enforces for you.
- `seats` (array): Players in turn order. Default: Player (human) then Agent (agent).
- `starter` (string): A ready-made game. Other fields here override its setup (for example seats).
- `title` (string)
- `turns` (string): alternate (default): one seat at a time. free: anyone acts anytime (guessing games, puzzles).

### `get_state` (~85 tokens)

See the game

What your seat can see now: the board, your hand, public piles, scores, dice, secrets you hold and the recent log. Call it when the player says they've moved or it might be your turn.

Input parameters:

- `agent_key` (string, required)
- `as` (string): Which of your seats, when you play more than one.
- `game_id` (string, required)

### `take_turn` (~379 tokens)

Make moves

Apply one or more actions for your seat, all or nothing: if any action is illegal, none happen and you get the reason. Usually end with end_turn. Action types and fields:
\- place {at: "B3"} or {column: "D"} with gravity; optional label, shape (disc, square, ring, star, diamond), color, kind, owner
\- move {from: "B3", to: "C4"} or {piece, to}; moving onto another player's piece takes it; optional label, kind
\- edit {at, owner?, label?, kind?, shape?, color?}: change a piece in place (flip, crown)
\- remove {at} or {piece}
\- mark {at, color?, label?}: paint or label a cell (hits, misses, letters)
\- draw {from?: "deck", to?: "hand", count?}
\- play {card, to?: "table", from?}: a card you can see, by id or label
\- give {card, to: seat}
\- shuffle {pile?}, collect {into?: "deck", from?: [piles]}: gather and reshuffle
\- roll {dice?: "2d6"}, pick {options: [...]}: server randomness, logged
\- score {counter?, seat?, add? | set?}
\- secret {name, value}: lock in hidden info (the word, the culprit, your fleet); reveal {name}
\- say {text}, end_turn {next?}, end_game {winner?, reason}, concede
Cells are column letter + row number from the top: A1 is the top left.

Input parameters:

- `actions` (array, required)
- `agent_key` (string, required)
- `as` (string)
- `game_id` (string, required)

### `show_board` (~48 tokens)

Show the board

Show the interactive board in the chat again, for example after a long conversation or when the player asks to see it.

Input parameters:

- `agent_key` (string, required)
- `game_id` (string, required)

### `delete_game` (~120 tokens)

Delete a game

Delete a game for good: the board, cards, log, secrets, seats and keys, and Playtable's record of it. Its link stops working. Only call this when the player asks. It needs the delete_code from the board in the chat where the game was made; you never get that code yourself, so ask the player to paste it. With a wrong code nothing is deleted. This can't be undone.

Input parameters:

- `delete_code` (string, required): Starts with del_. The player copies it from the board.
- `game_id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 63
- 2026-11-20: 63
- 2026-11-19: 62
- 2026-11-18: 62
- 2026-11-17: 61
- 2026-11-16: 61
- 2026-11-15: 60
- 2026-11-14: 60
- 2026-11-13: 59
- 2026-11-12: 59
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 64

## Common questions

### What is the Playtable MCP server?

Playtable is an MCP server listed in the public MCP registry as com.rowhousesoftware/playtable. Make up any game and play it in chat: a fair table that deals, hides cards and rolls dice. This page covers its hosted endpoint (https://play.rowhousesoftware.com/mcp).

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

Playtable scores 63 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 Playtable MCP server expose?

Playtable exposes 5 tools: create_game, get_state, take_turn, show_board, delete_game. Their descriptions and schemas cost roughly 1,071 tokens of context every time the server is loaded.

### Does the Playtable MCP server require authentication?

No. We connected to Playtable without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Playtable MCP server still maintained?

Playtable is still listed as active in the MCP registry. We last reached this channel on 21 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 Playtable MCP server?

VerifyMCP ran 13 checks on Playtable, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about Playtable: HTTPS. 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://play.rowhousesoftware.com/mcp
- Website: https://play.rowhousesoftware.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-rowhousesoftware-playtable/play.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rowhousesoftware-playtable/play/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-rowhousesoftware-playtable/play.json
- HTML version of this page: https://verifymcp.io/servers/com-rowhousesoftware-playtable/play
