# Screenbird (remote · mcp.screenbird.app)

Manage Screenbird digital signage screens: see what is live, show content, create designs.

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

## Components

- remote · `mcp.screenbird.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/app-screenbird-screenbird/mcp.md), [page](https://verifymcp.io/servers/app-screenbird-screenbird/mcp)

## Channel facts

- Endpoint: `https://mcp.screenbird.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

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

- **Endpoint Security**: 63/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 (push_content).
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1438 tokens (~119/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 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.

## Install

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

Screenbird is a hosted endpoint at https://mcp.screenbird.app/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 app-screenbird-screenbird 'https://mcp.screenbird.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-screenbird-screenbird": {
      "url": "https://mcp.screenbird.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-screenbird-screenbird": {
      "type": "http",
      "url": "https://mcp.screenbird.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-screenbird-screenbird]
url = "https://mcp.screenbird.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add app-screenbird-screenbird --url 'https://mcp.screenbird.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-screenbird-screenbird:
    url: "https://mcp.screenbird.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-screenbird-screenbird": {
      "Transport": "http",
      "Url": "https://mcp.screenbird.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-screenbird-screenbird -t streamable-http -u 'https://mcp.screenbird.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-screenbird-screenbird": {
      "type": "http",
      "url": "https://mcp.screenbird.app/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-04 (score 71, +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-02 (score 70, +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-10-31 (score 69, +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-10-30 (score 68, +2)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 62% → 100%
- [cosmetic] “activate_scene” reworded the description of “scene_id”
- [cosmetic] “check_device” reworded the description of “device”
- [cosmetic] “get_install_steps” reworded the description of “device”
- [cosmetic] “push_content” reworded the description of “content_id”
- [cosmetic] “push_content” reworded the description of “screen_id”
- [cosmetic] “push_content” reworded the description of “subscreen_id”
- [cosmetic] “release_scene” reworded the description of “scene_id”
- [cosmetic] “release_screen” reworded the description of “screen_id”
- [cosmetic] “release_screen” reworded the description of “subscreen_id”
- [cosmetic] “search_content” reworded the description of “type”

### 2026-10-28 (score 66, +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-10-27 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 65)

First indexed and scored.

## MCP tools (12)

### `list_screens` (~147 tokens)

List screens

List the connected team's screens: online status and what each screen and sub-screen shows right now (its normal content, pushed content, a scene or screen mirroring), with the end time if there is one. Also returns the account's time zone and current local time. Filter with query (part of a screen or sub-screen name) or screen_id. Results come in pages: pass next_cursor as cursor for the next page.

Input parameters:

- `cursor` (string): next_cursor from the previous page.
- `limit` (integer): Screens per page. Default 25.
- `query` (string): Part of a screen or sub-screen name.
- `screen_id` (string): One screen.

### `search_content` (~92 tokens)

Search content

Search the team's content that can be shown on a screen: files, designs, apps, split screens and playlists. Newest first. Returns the id, name and type of each item.

Input parameters:

- `limit` (integer): Default 20.
- `query` (string): Part of the name. Leave empty to list recent content.
- `type` (string): Only content of this type. Leave out for all types.

### `push_content` (~247 tokens)

Show content on a screen

Show content on one screen, or on one sub-screen of a split screen, in place of what it shows now, until a time or until it is put back to normal. A split screen needs a subscreen_id. Returns what the screen shows afterwards. Content only appears once the screen is online and has a player paired; the result includes online and paired when the connection may read screens.

Input parameters:

- `content_id` (string, required): Id of the file, design, app, split screen or playlist to show, as found in the team's content.
- `screen_id` (string, required): Id of the screen, as listed with the team's screens.
- `subscreen_id` (string): Id of one sub-screen of a split screen. Required for a split screen, left out for a normal screen.
- `until` (string): When to go back to normal: local time of the account without an offset (for example 2026-10-23T18:00), or a time with an offset (2026-10-23T18:00:00+02:00). At most 90 days ahead. Leave out to show i…

### `release_screen` (~77 tokens)

Put a screen back to normal

End pushed content or a scene on one screen or sub-screen; it goes back to its own content.

Input parameters:

- `screen_id` (string, required): Id of the screen, as listed with the team's screens.
- `subscreen_id` (string): Id of one sub-screen of a split screen. Leave out to put the whole screen back to normal.

### `list_scenes` (~102 tokens)

List scenes

List the team's scenes in their order, with their state (live, partly live, changed since it went live, off) and which screens and sub-screens each scene sets (at most 20 targets per scene; targets_total is the real number). Results come in pages: pass next_cursor as cursor for the next page.

Input parameters:

- `cursor` (string): next_cursor from the previous page.
- `limit` (integer): Scenes per page. Default 25.

### `activate_scene` (~90 tokens)

Start a scene

Put a scene live: every screen and sub-screen in the scene switches at once, in place of what it shows. Running it again puts changes to the scene live. A screen only shows the scene once it is online and has a player paired; each result includes online and paired when the connection may read screens.

Input parameters:

- `scene_id` (string, required): Id of the scene, as listed with the team's scenes.

### `release_scene` (~40 tokens)

Put a scene back to normal

End one scene: its screens go back to their own content.

Input parameters:

- `scene_id` (string, required): Id of the scene, as listed with the team's scenes.

### `release_all` (~26 tokens)

Put everything back to normal

End all scenes and all pushed content on the team's screens. Screen mirroring keeps running.

### `create_design` (~186 tokens)

Create a design

Create a design (a full-screen slide for a screen, such as a menu, an announcement or an event poster) from a description. It picks a fitting template, fills in the text and adds stock photos where the template has them; no images are generated with AI. The design is saved in the team's files and can be shown on a screen or used in a scene. Each design uses the account's AI budget, with at most 20 designs per hour.

Input parameters:

- `brief` (string, required): What the design must show, in the user's words, with all texts, prices, times and names to put on it.
- `language` (string): Two-letter language code of the texts on the design (en, nl, de, ...).
- `name` (string): Name of the design in Screenbird. Optional.
- `orientation` (string): Screen orientation. Default landscape.

### `search_help` (~111 tokens)

Search Screenbird help

Search the Screenbird help center (how features work, setup, troubleshooting). Returns up to 3 articles with title, summary and link; set full to true for the complete text of each article.

Input parameters:

- `full` (boolean): Return the complete article text. Default false.
- `language` (string): Two-letter language code of the user (en, nl, de, fr, ...). Articles come in that language.
- `query` (string, required): What the user wants to know, in their own words.

### `get_install_steps` (~97 tokens)

Get install steps for a player

Steps to install the Screenbird player on a device type, ending with the pairing code that the user enters in the dashboard.

Input parameters:

- `device` (string, required): Device to install the player on: signage_stick = Amazon Signage Stick, fire_tv = Fire TV Stick or Cube, android_tv = Android TV or Google TV, windows / macos / linux / raspberry_pi = computer, browse…

### `check_device` (~89 tokens)

Check if a device works

Check whether a device (as the user names it, for example "Samsung TV", "Chromecast", "iPad") works with Screenbird. Returns works, coming_soon, does_not_work, works_in_browser or unknown, with an explanation.

Input parameters:

- `device` (string, required): The device as the user names it: brand, model or type (for example "Samsung TV", "Chromecast").

## Diagnostics

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

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 66
- 2026-10-28: 66
- 2026-10-27: 65
- 2026-10-26: 65

## Common questions

### What is the Screenbird MCP server?

Screenbird is an MCP server listed in the public MCP registry as app.screenbird/screenbird. Manage Screenbird digital signage screens: see what is live, show content, create designs. This page covers its hosted endpoint (https://mcp.screenbird.app/mcp).

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

Screenbird scores 71 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 Screenbird MCP server expose?

Screenbird exposes 12 tools: list_screens, search_content, push_content, release_screen, list_scenes, and 7 more. Their descriptions and schemas cost roughly 1,304 tokens of context every time the server is loaded.

### Does the Screenbird MCP server require authentication?

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

### Is the Screenbird MCP server still maintained?

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

VerifyMCP ran 13 checks on Screenbird, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.screenbird.app/mcp
- Website: https://screenbird.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-screenbird-screenbird/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-screenbird-screenbird/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-screenbird-screenbird/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-screenbird-screenbird/mcp