# io.github.bea-technology/roxyon (npm · @roxyon/mcp)

Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.

- Trust score: 88/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.roxyon.com`: 36/100, [markdown](https://verifymcp.io/servers/bea-technology-roxyon/mcp.md), [page](https://verifymcp.io/servers/bea-technology-roxyon/mcp)
- npm · `@roxyon/mcp`: 88/100 (this document), [markdown](https://verifymcp.io/servers/bea-technology-roxyon/roxyon-mcp.md), [page](https://verifymcp.io/servers/bea-technology-roxyon/roxyon-mcp)

## Channel facts

- Registry: `npm`
- Package: `@roxyon/mcp`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 34 of 105 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to bea-technology/roxyon-devtools).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 84/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).
  - Tool/resource definitions use about 1384 tokens (~72/item across 19 items; 15 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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).
  - 51% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "roxyon_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 17 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 io.github.bea-technology/roxyon MCP server?

io.github.bea-technology/roxyon runs locally as an npm package, launched with npx -y @roxyon/mcp. 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 bea-technology-roxyon -- npx -y @roxyon/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "bea-technology-roxyon": {
      "command": "npx",
      "args": [
        "-y",
        "@roxyon/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bea-technology-roxyon": {
      "command": "npx",
      "args": [
        "-y",
        "@roxyon/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add bea-technology-roxyon -- npx -y @roxyon/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bea-technology-roxyon": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@roxyon/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bea-technology-roxyon --command npx --arg -y --arg @roxyon/mcp
```

### Hermes

```yaml
mcp_servers:
  bea-technology-roxyon:
    command: "npx"
    args: ["-y", "@roxyon/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "bea-technology-roxyon": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@roxyon/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add bea-technology-roxyon -t stdio -c npx -a -y @roxyon/mcp
```

### Other

```json
{
  "mcpServers": {
    "bea-technology-roxyon": {
      "command": "npx",
      "args": [
        "-y",
        "@roxyon/mcp"
      ]
    }
  }
}
```

## 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-09-20 (score 88, +1)

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

### 2026-09-18 (score 87, +1)

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

### 2026-09-16 (score 86, +1)

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

### 2026-09-14 (score 85, +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-09-12 (score 84, +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-09-10 (score 83, +1)

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

### 2026-09-07 (score 82, +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-09-05 (score 81, +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.

## MCP tools (15)

### `roxyon_whoami` (~28 tokens)

Roxyon: who am I

Show the signed-in Roxyon user and their subscriptions (which one is active).

### `roxyon_list_domains` (~27 tokens)

Roxyon: list hosts

List the domains (hosts) on the active subscription — the possible deploy targets.

### `roxyon_list_apps` (~24 tokens)

Roxyon: list applications

List the applications on the active subscription with their status and revision.

### `roxyon_init` (~107 tokens)

Roxyon: initialise a project

Detect a project's type and write roxyon.json. Run this once per project before roxyon_deploy. Does not create anything on the platform.

Input parameters:

- `dir` (string, required): Absolute path to the project directory.
- `folder` (string): Sub-path under the host; "" = site root.
- `host` (string): Deploy host (a domain on the subscription).
- `overwrite` (boolean): Replace an existing roxyon.json.
- `runtime` (string)

### `roxyon_deploy` (~160 tokens)

Roxyon: deploy a project

Build (if configured) and deploy the project in "dir" to Roxyon. Without confirm:true this returns a dry-run plan (what would build, where it would go, how many files). With confirm:true it runs the build, uploads, and — for app runtimes — waits for it to go live. Requires roxyon.json (run roxyon_init first).

Input parameters:

- `build` (boolean): Run the configured build command (default true).
- `confirm` (boolean): Actually deploy. Omit for a dry-run plan.
- `dir` (string, required): Absolute path to the project directory (must contain roxyon.json).
- `follow` (boolean): For app runtimes, wait until running/failed (default true).

### `roxyon_app_status` (~53 tokens)

Roxyon: application status

Current status, revisions and last error for an application (by id or project dir).

Input parameters:

- `application` (string)
- `dir` (string): A project directory whose roxyon.json links an application.

### `roxyon_logs` (~51 tokens)

Roxyon: application logs

Recent journal lines for an application (by id or project dir).

Input parameters:

- `application` (string)
- `dir` (string)
- `lines` (integer): How many lines (default 100).

### `roxyon_restart` (~43 tokens)

Roxyon: restart an application

Bounce the application process (no rebuild). Needs confirm:true.

Input parameters:

- `application` (string)
- `confirm` (boolean)
- `dir` (string)

### `roxyon_env_get` (~34 tokens)

Roxyon: read environment variables

An application's environment variables as KEY=value lines.

Input parameters:

- `application` (string)
- `dir` (string)

### `roxyon_env_set` (~93 tokens)

Roxyon: set environment variables

Merge variables into an application's environment and bump its revision. Run roxyon_deploy afterwards to apply. Needs confirm:true. PORT and HOST are platform-managed and ignored.

Input parameters:

- `application` (string)
- `confirm` (boolean)
- `dir` (string)
- `remove` (array): Keys to delete.
- `vars` (object, required): { KEY: "value", ... } to set.

### `roxyon_link_github` (~99 tokens)

Roxyon: connect a git remote

Connect a git repository to an application for push-to-deploy. Returns the deploy key and webhook URL to add to the repo. Needs confirm:true.

Input parameters:

- `application` (string)
- `branch` (string): Branch to deploy (default main).
- `confirm` (boolean)
- `dir` (string)
- `repoUrl` (string, required): SSH git URL, e.g. git@github.com:you/app.git

### `roxyon_add_domain` (~130 tokens)

Roxyon: add a subdomain / host

Provision a host — DNS + web server + automatic HTTPS. The host must be a subdomain of a domain the account already hosts (or a *.roxyon.com subdomain). Returns while it is still coming up; TLS follows a minute or two later. Needs confirm:true.

Input parameters:

- `confirm` (boolean)
- `host` (string, required): The full hostname, e.g. promo.mycompany.com
- `spa` (boolean): Single-page app: unmatched paths serve /index.html.
- `subscription` (string): Which subscription to attach it to (omit if the account has one).

### `roxyon_deploy_content` (~175 tokens)

Roxyon: deploy generated files

Publish a set of files you generated (HTML/CSS/JS/assets) to a host on the account. The host must already exist (roxyon_add_domain, or an existing site). Overlay by default — pass clean:true to replace the whole document root. Needs confirm:true. Limits: 60 files, 1024 KB per file, 2.0 MB total (base64-encode binaries).

Input parameters:

- `clean` (boolean): Replace the whole docroot (keeps .well-known).
- `confirm` (boolean)
- `files` (array, required)
- `folder` (string): Sub-path under the host; "" = site root.
- `host` (string, required): Target host, e.g. promo.mycompany.com
- `spa` (boolean): Also flip the host to SPA routing.

### `roxyon_list_files` (~49 tokens)

Roxyon: list a site’s files

The files currently deployed to a host's document root.

Input parameters:

- `folder` (string)
- `host` (string, required)
- `path` (string): List under this sub-path only.

### `roxyon_read_file` (~56 tokens)

Roxyon: read a site file

Read one file from a host's document root (to review or edit it).

Input parameters:

- `folder` (string)
- `host` (string, required)
- `path` (string, required): Relative path, e.g. index.html

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/bea-technology-roxyon/roxyon-mcp#diagnostics

## Score history

- 2026-09-20: 88
- 2026-09-19: 87
- 2026-09-18: 87
- 2026-09-17: 86
- 2026-09-16: 86
- 2026-09-15: 85
- 2026-09-14: 85
- 2026-09-13: 84
- 2026-09-12: 84
- 2026-09-11: 83
- 2026-09-10: 83
- 2026-09-09: 82
- 2026-09-08: 82
- 2026-09-07: 82
- 2026-09-06: 81
- 2026-09-05: 81
- 2026-09-04: 80
- 2026-09-03: 80
- 2026-09-02: 54

## Common questions

### What is the io.github.bea-technology/roxyon MCP server?

io.github.bea-technology/roxyon is an MCP server listed in the public MCP registry as io.github.bea-technology/roxyon. Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure. This page covers its npm package (@roxyon/mcp).

### Is the io.github.bea-technology/roxyon MCP server safe to use?

io.github.bea-technology/roxyon scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.bea-technology/roxyon MCP server expose?

io.github.bea-technology/roxyon exposes 15 tools: roxyon_whoami, roxyon_list_domains, roxyon_list_apps, roxyon_init, roxyon_deploy, and 10 more. Their descriptions and schemas cost roughly 1,129 tokens of context every time the server is loaded.

### Is the io.github.bea-technology/roxyon MCP server still maintained?

io.github.bea-technology/roxyon is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.bea-technology/roxyon MCP server under?

io.github.bea-technology/roxyon declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@roxyon/mcp
- Socket report: https://socket.dev/npm/package/@roxyon/mcp
- Repository: https://github.com/bea-technology/roxyon-devtools
- Changelog RSS feed: https://verifymcp.io/servers/bea-technology-roxyon/roxyon-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bea-technology-roxyon/roxyon-mcp.json
- HTML version of this page: https://verifymcp.io/servers/bea-technology-roxyon/roxyon-mcp