Hostbeam
NPM · @HOSTBEAM/MCP · SCANNED OCT 2
Lets a coding agent read the screenshots you beam to its server with Hostbeam.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 298 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Hostbeam MCP server?
Hostbeam runs locally as an npm package, launched with npx -y @hostbeam/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @hostbeam/mcp
claude mcp add app-hostbeam-mcp -- npx -y @hostbeam/mcp
{
"mcpServers": {
"app-hostbeam-mcp": {
"command": "npx",
"args": [
"-y",
"@hostbeam/mcp"
]
}
}
} {
"servers": {
"app-hostbeam-mcp": {
"command": "npx",
"args": [
"-y",
"@hostbeam/mcp"
]
}
}
} codex mcp add app-hostbeam-mcp -- npx -y @hostbeam/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-hostbeam-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@hostbeam/mcp"
],
"enabled": true
}
}
} openclaw mcp add app-hostbeam-mcp --command npx --arg -y --arg @hostbeam/mcp
mcp_servers:
app-hostbeam-mcp:
command: "npx"
args: ["-y", "@hostbeam/mcp"] {
"McpServers": {
"app-hostbeam-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@hostbeam/mcp"
]
}
}
} assistant mcp add app-hostbeam-mcp -t stdio -c npx -a -y @hostbeam/mcp
{
"mcpServers": {
"app-hostbeam-mcp": {
"command": "npx",
"args": [
"-y",
"@hostbeam/mcp"
]
}
}
} 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.
- 1 Oct 26 +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.
- 29 Sept 26 +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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 21 Sept 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.
- 19 Sept 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.
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 2 Oct 2026 · Analysed npm/@hostbeam/mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
latest_screenshot Latest screenshot ~99
Read the latest beam: every screenshot the user sent to this host with Hostbeam in one gesture (several, if they beamed several), with how long ago it arrived. Use this when they refer to a screenshot, to something being broken on screen, or ask you to look at what they are seeing. If it does not match what they describe, or arrived long before they asked, say so rather than assuming it is what they meant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_screenshots List screenshots ~65
List the screenshots the user has beamed to this host, grouped by beam, newest first, with sizes and how long ago. Metadata only — no image data — so it is cheap to call before deciding which to read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 10. |
No output schema declared.
No examples provided.
read_screenshot Read screenshot ~58
Read one specific beamed screenshot by its file name, as listed by list_screenshots.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A file name exactly as list_screenshots gives it, such as hostbeam-1788875278869.png. |
No output schema declared.
No examples provided.
What is the Hostbeam MCP server?
Hostbeam is an MCP server listed in the public MCP registry as app.hostbeam/mcp. Lets a coding agent read the screenshots you beam to its server with Hostbeam. This page covers its npm package (@hostbeam/mcp).
Is the Hostbeam MCP server safe to use?
Hostbeam scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. It declares no install or post-install scripts. 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 Hostbeam MCP server expose?
Hostbeam exposes 3 tools: latest_screenshot, list_screenshots, read_screenshot. Their descriptions and schemas cost roughly 222 tokens of context every time the server is loaded.
Is the Hostbeam MCP server still maintained?
Hostbeam is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Hostbeam MCP server under?
Hostbeam declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.