Beamline UI
REMOTE · MCP.BEAMLINE.IO
React UI parts your agent copies into your repo as code you own: 200+ components, 50+ screens.
Available components
Last scanned (22 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 27 Oct 26 +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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 +31
- Authorization: pass → partial ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 10 Oct 26 40
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.beamline.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=beamline.io | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 29f8b0e50c6662da13d50fc0709f8bb5 |
| SANs: beamline.io, mcp.beamline.io, *.mcp.beamline.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.beamline.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| beamline.io. | present | 2371 | 13 | Verified |
| mcp.beamline.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.beamline.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.beamline.io/mcp | HTTPS enforced | 301 | https://mcp.beamline.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
beamline_capabilities ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| part | number | – | Which part (1 = the guide, default). Each answer names the next. |
No output schema declared.
No examples provided.
beamline_component ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | – | yes | 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). |
No output schema declared.
No examples provided.
beamline_install ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | – | yes | 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. |
No output schema declared.
No examples provided.
beamline_picture ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | One element id from beamline_capabilities. |
| theme | string | – | Sheet theme; default dark. Both use the default Prism look. |
No output schema declared.
No examples provided.
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.
remote · mcp.beamline.io
claude mcp add --transport http io-beamline-beamline 'https://mcp.beamline.io/mcp'
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 76 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.