# io.github.dbhq-uk/heliograph (npm · @dbhq/heliograph)

Run commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled.

- Trust score: 43/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- npm · `@dbhq/heliograph`: 43/100 (this document), [markdown](https://verifymcp.io/servers/dbhq-uk-heliograph/dbhq-heliograph.md), [page](https://verifymcp.io/servers/dbhq-uk-heliograph/dbhq-heliograph)

## Channel facts

- Registry: `npm`
- Package: `@dbhq/heliograph`
- Version: `0.3.2`
- 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-27.

- **Supply Chain Security**: 94/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 74/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to dbhq-uk/heliograph).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it.

## Install

### How do I install the io.github.dbhq-uk/heliograph MCP server?

io.github.dbhq-uk/heliograph runs locally as an npm package, launched with npx -y @dbhq/heliograph. 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 dbhq-uk-heliograph -- npx -y @dbhq/heliograph
```

### Cursor

```json
{
  "mcpServers": {
    "dbhq-uk-heliograph": {
      "command": "npx",
      "args": [
        "-y",
        "@dbhq/heliograph"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dbhq-uk-heliograph": {
      "command": "npx",
      "args": [
        "-y",
        "@dbhq/heliograph"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dbhq-uk-heliograph -- npx -y @dbhq/heliograph
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dbhq-uk-heliograph --command npx --arg -y --arg @dbhq/heliograph
```

### Hermes

```yaml
mcp_servers:
  dbhq-uk-heliograph:
    command: "npx"
    args: ["-y", "@dbhq/heliograph"]
```

### Netclaw

```json
{
  "McpServers": {
    "dbhq-uk-heliograph": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@dbhq/heliograph"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dbhq-uk-heliograph -t stdio -c npx -a -y @dbhq/heliograph
```

### Other

```json
{
  "mcpServers": {
    "dbhq-uk-heliograph": {
      "command": "npx",
      "args": [
        "-y",
        "@dbhq/heliograph"
      ]
    }
  }
}
```

## 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-25 (score 43, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-17 (score 43, −5)

- [security regression] Source repository: pass → fail

### 2026-09-11 (score 48)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dbhq-uk-heliograph/dbhq-heliograph#diagnostics

## Score history

- 2026-09-27: 43
- 2026-09-26: 43
- 2026-09-25: 43
- 2026-09-24: 43
- 2026-09-23: 43
- 2026-09-22: 43
- 2026-09-21: 43
- 2026-09-20: 43
- 2026-09-19: 43
- 2026-09-18: 43
- 2026-09-17: 43
- 2026-09-16: 48
- 2026-09-15: 48
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 48

## Common questions

### What is the io.github.dbhq-uk/heliograph MCP server?

io.github.dbhq-uk/heliograph is an MCP server listed in the public MCP registry as io.github.dbhq-uk/heliograph. Run commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled. This page covers its npm package (@dbhq/heliograph).

### Is the io.github.dbhq-uk/heliograph MCP server safe to use?

io.github.dbhq-uk/heliograph scores 43 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. 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.

### Is the io.github.dbhq-uk/heliograph MCP server still maintained?

io.github.dbhq-uk/heliograph is still listed as active in the MCP registry. We last reached this channel on 27 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.dbhq-uk/heliograph MCP server under?

io.github.dbhq-uk/heliograph 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/@dbhq/heliograph
- Socket report: https://socket.dev/npm/package/@dbhq/heliograph
- Website: https://heliograph.dbhq.uk/
- Changelog RSS feed: https://verifymcp.io/servers/dbhq-uk-heliograph/dbhq-heliograph.xml
- Changelog JSON feed: https://verifymcp.io/servers/dbhq-uk-heliograph/dbhq-heliograph.json
- HTML version of this page: https://verifymcp.io/servers/dbhq-uk-heliograph/dbhq-heliograph