# Dunstan (npm · dunstan)

Checks a coding agent's handback against the pull request's GitHub record. No model decides.

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `dunstan`: 80/100 (this document), [markdown](https://verifymcp.io/servers/barglabs-dunstan/dunstan.md), [page](https://verifymcp.io/servers/barglabs-dunstan/dunstan)

## Channel facts

- Registry: `npm`
- Package: `dunstan`
- Version: `0.1.12`
- 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-10-17.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to BargLabs/dunstan).
  - Clear OSI-approved license (AGPL-3.0-only).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 577 tokens (~288/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Dunstan MCP server?

Dunstan runs locally as an npm package, launched with npx -y dunstan. 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 barglabs-dunstan -- npx -y dunstan
```

### Cursor

```json
{
  "mcpServers": {
    "barglabs-dunstan": {
      "command": "npx",
      "args": [
        "-y",
        "dunstan"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "barglabs-dunstan": {
      "command": "npx",
      "args": [
        "-y",
        "dunstan"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add barglabs-dunstan -- npx -y dunstan
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add barglabs-dunstan --command npx --arg -y --arg dunstan
```

### Hermes

```yaml
mcp_servers:
  barglabs-dunstan:
    command: "npx"
    args: ["-y", "dunstan"]
```

### Netclaw

```json
{
  "McpServers": {
    "barglabs-dunstan": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "dunstan"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add barglabs-dunstan -t stdio -c npx -a -y dunstan
```

### Other

```json
{
  "mcpServers": {
    "barglabs-dunstan": {
      "command": "npx",
      "args": [
        "-y",
        "dunstan"
      ]
    }
  }
}
```

## 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-10-17 (score 80, +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-16 (score 79, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-15 (score 68, +30)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Dependency health: unverified → pass
- [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] Package version: 0.1.10 → 0.1.12
- [functional] Package version: 0.1.10 → 0.1.11

### 2026-10-14 (score 38, −11)

- [security regression] Known CVEs: pass → unverified
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [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] Package version: 0.1.8 → 0.1.10
- [functional] Package version: 0.1.8 → 0.1.9

### 2026-10-13 (score 49, 0)

- [functional regression] Security disclosure: unverified → fail
- [functional] Package version: 0.1.6 → 0.1.8
- [functional] Package version: 0.1.6 → 0.1.7

### 2026-10-12 (score 49)

First indexed and scored.

## MCP tools (2)

### `dunstan_check_handback` (~332 tokens)

Check a handback against the record

Check a completion handback against the repository's own record, before you say done. Give the subject (repository owner/name and pull request number) and exactly one of: block, the dunstan-handback block as a JSON object; or report, the report text that carries exactly one ```dunstan-handback fence. Of the checks claims, checks.allSucceeded is true only if every counted check run concluded success, so a skipped or neutral run makes it false; checks.noneFailed is true if none concluded other than success, skipped or neutral and at least one succeeded. Returns the verdict (pass, fail or unverifiable), the claims table, and the full record as JSON. Same checker and same verdict as `dunstan check` on the same evidence; no model decides. Reads GitHub metadata with GITHUB_TOKEN and writes nothing to GitHub or the repository; the record is written to a file only when you pass outPath. If the verdict is not pass, report the rows as they are; change the work, not the block.

Input parameters:

- `block` (object): The dunstan-handback block as a JSON object. Give this or report, not both.
- `outPath` (string): Write the record to this path (must not exist). Without it nothing is written.
- `pullRequest` (integer, required): The pull request number the handback is about.
- `report` (string): The report text, carrying exactly one ```dunstan-handback fence. Give this or block, not both.
- `repository` (string, required): The GitHub repository, owner/name.

### `dunstan_suggest_declarations` (~131 tokens)

Suggest declarations from the prose

List the sentences in your report's prose that look like claims your dunstan-handback block does not declare, before you say done. Give report, the report text. For each, declare it in the block, or reword it if it is not a claim about this PR. Offline: needs no pull request, reads nothing and writes nothing. Never a verdict: nothing passes or fails, and nothing is written to a record. The same text as `dunstan suggest`.

Input parameters:

- `report` (string, required): The report text: the prose and its ```dunstan-handback fence.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/barglabs-dunstan/dunstan#diagnostics

## Score history

- 2026-10-17: 80
- 2026-10-16: 79
- 2026-10-15: 68
- 2026-10-14: 38
- 2026-10-13: 49
- 2026-10-12: 49

## Common questions

### What is the Dunstan MCP server?

Dunstan is an MCP server listed in the public MCP registry as io.github.BargLabs/dunstan. Checks a coding agent's handback against the pull request's GitHub record. No model decides. This page covers its npm package (dunstan).

### Is the Dunstan MCP server safe to use?

Dunstan scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Dunstan MCP server expose?

Dunstan exposes 2 tools: dunstan_check_handback, dunstan_suggest_declarations. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.

### Is the Dunstan MCP server still maintained?

Dunstan is still listed as active in the MCP registry. We last reached this channel on 17 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 Dunstan MCP server under?

Dunstan declares the AGPL-3.0-only 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/dunstan
- Socket report: https://socket.dev/npm/package/dunstan
- Repository: https://github.com/BargLabs/dunstan
- Website: https://barglabs.ai/dunstan
- Changelog RSS feed: https://verifymcp.io/servers/barglabs-dunstan/dunstan.xml
- Changelog JSON feed: https://verifymcp.io/servers/barglabs-dunstan/dunstan.json
- HTML version of this page: https://verifymcp.io/servers/barglabs-dunstan/dunstan