# Canary (npm · @mindstone/mcp-server-canary)

Mindstone-internal release-pipeline test connector; not for use. Single ping tool; no auth.

- Trust score: 87/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-11

## Components

- npm · `@mindstone/mcp-server-canary`: 87/100 (this document), [markdown](https://verifymcp.io/servers/mindstone-mcp-server-canary/mindstone-mcp-server-canary.md), [page](https://verifymcp.io/servers/mindstone-mcp-server-canary/mindstone-mcp-server-canary)

## Channel facts

- Registry: `npm`
- Package: `@mindstone/mcp-server-canary`
- Version: `0.0.4`
- 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-08-11.

- **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.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 87/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to mindstone/mcp-servers).
  - License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license.
  - Actively maintained (last published 60 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 58 tokens (~58/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add mindstone-mcp-server-canary -- npx -y @mindstone/mcp-server-canary
```

### Codex

```bash
codex mcp add mindstone-mcp-server-canary -- npx -y @mindstone/mcp-server-canary
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mindstone-mcp-server-canary --command npx --arg -y --arg @mindstone/mcp-server-canary
```

### Hermes

```yaml
mcp_servers:
  mindstone-mcp-server-canary:
    command: "npx"
    args: ["-y", "@mindstone/mcp-server-canary"]
```

### Other

```json
{
  "mcpServers": {
    "mindstone-mcp-server-canary": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-canary"
      ]
    }
  }
}
```

## 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-08-11 (score 87, +3)

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

### 2026-08-09 (score 84, +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.

### 2026-08-08 (score 83, +4)

- [security improvement] Known CVEs: partial → pass
- [functional improvement] Security disclosure: fail → pass
- [functional] Dependency health: partial → 0.85

### 2026-08-07 (score 79, +1)

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

### 2026-08-05 (score 78, +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.

### 2026-08-04 (score 77, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 73, +52)

- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Provenance: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [security] The attested source repository moved: mindstone/mcp-servers
- [functional regression] License: unverified → fail
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: FSL-1.1-MIT

### 2026-08-01 (score 21, −4)

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

## MCP tools (1)

### `ping` (~58 tokens)

Echo a message back wrapped as "pong v3: <message>". Used to verify the canary connector is reachable and the release pipeline produced a working build.

Input parameters:

- `message` (string, required): A short message to echo back. 1-200 chars.

## Diagnostics

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

## Score history

- 2026-08-11: 87
- 2026-08-10: 84
- 2026-08-09: 84
- 2026-08-08: 83
- 2026-08-07: 79
- 2026-08-06: 78
- 2026-08-05: 78
- 2026-08-04: 77
- 2026-08-03: 73
- 2026-08-02: 73
- 2026-08-01: 21
- 2026-07-31: 25
- 2026-07-29: 25
- 2026-07-28: 24
- 2026-07-27: 46

## Links

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