# Beamline UI (remote · mcp.beamline.io)

React UI parts your agent copies into your repo as code you own: 200+ components, 50+ screens.

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.beamline.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.2`

## 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**: 83/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 is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1143 tokens (~285/item across 4 items; 4 tools + 0 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**: 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Beamline UI MCP server?

Beamline UI is a hosted endpoint at https://mcp.beamline.io/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 io-beamline-beamline 'https://mcp.beamline.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-beamline-beamline": {
      "url": "https://mcp.beamline.io/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.io-beamline-beamline]
url = "https://mcp.beamline.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-beamline-beamline --url 'https://mcp.beamline.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-beamline-beamline:
    url: "https://mcp.beamline.io/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add io-beamline-beamline -t streamable-http -u 'https://mcp.beamline.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-beamline-beamline": {
      "type": "http",
      "url": "https://mcp.beamline.io/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-05 (score 77, +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-11-03 (score 76, +1)

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

### 2026-10-31 (score 75, +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-29 (score 74, +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-28 (score 73, 0)

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

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

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 71, +31)

- [security regression] Authorization: pass → partial
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

## MCP tools (4)

### `beamline_capabilities` (~131 tokens)

The complete Beamline library and how to choose from it: a selection guide (screens and kits, data → control, screen craft, looks and install), then every screen and component with what it is for and what to use instead.
Call it before designing and read every part in order; each answer names the next. Choose by the person's workflow and data: a block when its job, data and actions fit, otherwise the parts it is composed from; the most specific element for every item.

Input parameters:

- `part` (number): Which part (1 = the guide, default). Each answer names the next.

### `beamline_component` (~189 tokens)

Exact details of Beamline elements: the import, required and typed props, states, keyboard, motion, the parts to style and working examples to copy.
Call it for every element you chose, blocks included, before writing code with it; never guess props. Many ids come back in parts: call again with the same ids and the next part. A block's compose: lines list the parts it is built from, your kit when it fits only partly. Examples use gallery data; pass your own records in the documented types. A 🔒 element returns its description and uses, without code or props. Not for choosing elements: that is beamline_capabilities.

Input parameters:

- `ids` (required): Element ids from beamline_capabilities, e.g. ["data-grid", "number-field"].
- `part` (number): Which part, when many elements come back in parts (each part names the next).

### `beamline_install` (~269 tokens)

One command that adds the chosen Beamline elements and a look (default prism) to the app: only those packages, one stylesheet and the look.
Pass every element the screens need in one call; call it again to add more later. Run the command in the app folder, import the stylesheet once and pass the installed look to UIRoot. In an app that already has Beamline, pass installed (its release): the answer says when a newer one is out. Elements outside the person's packs are refused, naming the pack that has them.

Input parameters:

- `ids` (required): Every element the screens need, by id from beamline_capabilities.
- `installed` (string): The Beamline release the app already uses, if any: acceptedRelease.version in .beamline/package-selection.json (beamline-ui.lock.json for editable source). The answer then says when a newer one is ou…
- `look` (string): prism, soft, blueprint, glass, metal, glow, pop, mono or ink (default prism: black, neutral glass, white main action).
- `source` (boolean): True for every Beamline file as editable source in the app, including runtime, foundation, selected looks and fonts; no @beamline dependencies. Needs Tailwind v4. Default false: compiled packages.

### `beamline_picture` (~122 tokens)

Inspect a candidate's layout and states, compare plausible choices, or show the person how a part looks. Returns one labelled states sheet in dark or light Prism and a public URL. Pictures of 🔒 elements are available too; their code still needs access. Choose pictures that resolve a design question rather than requesting the whole catalogue. This previews a library part, not the app you compose from it.

Input parameters:

- `id` (string, required): One element id from beamline_capabilities.
- `theme` (string): Sheet theme; default dark. Both use the default Prism look.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Beamline UI MCP server?

Beamline UI is an MCP server listed in the public MCP registry as io.beamline/beamline. React UI parts your agent copies into your repo as code you own: 200+ components, 50+ screens. This page covers its hosted endpoint (https://mcp.beamline.io/mcp).

### Is the Beamline UI MCP server safe to use?

Beamline UI scores 77 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 Beamline UI MCP server expose?

Beamline UI exposes 4 tools: beamline_capabilities, beamline_component, beamline_install, beamline_picture. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.

### Does the Beamline UI MCP server require authentication?

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

### Is the Beamline UI MCP server still maintained?

Beamline UI 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.

## Links

- Remote endpoint: https://mcp.beamline.io/mcp
- Website: https://beamline.io/connect
- Changelog RSS feed: https://verifymcp.io/servers/io-beamline-beamline/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-beamline-beamline/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-beamline-beamline/mcp