Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Canary

NPM · @MINDSTONE/MCP-SERVER-CANARY · SCANNED AUG 11

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

Available components

npm · @mindstone/mcp-server-canary 87
+10 this week 87 Trust /100
Trust breakdown (6 categories)

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 →

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @mindstone/mcp-server-canary

# add to Claude Code
claude mcp add mindstone-mcp-server-canary -- npx -y @mindstone/mcp-server-canary
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add mindstone-mcp-server-canary --command npx --arg -y --arg @mindstone/mcp-server-canary
# ~/.hermes/config.yaml
mcp_servers:
  mindstone-mcp-server-canary:
    command: "npx"
    args: ["-y", "@mindstone/mcp-server-canary"]
// mcp.json
{
  "mcpServers": {
    "mindstone-mcp-server-canary": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-canary"
      ]
    }
  }
}
Changelog

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.

  • 11 Aug 26 +3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 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.

  • 8 Aug 26 +4
    • Known CVEs: partial → pass ▲ security
    • Security disclosure: fail → pass ▲ functional
    • Dependency health: partial → 0.85 functional
  • 7 Aug 26 +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.

  • 5 Aug 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.

  • 4 Aug 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 2 Aug 26 +52
    • Known CVEs: unverified → partial ▲ security
    • Install scripts: unverified → pass ▲ security
    • Provenance: unverified → pass ▲ security
    • 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 security
    • License: unverified → fail ▼ functional
    • Schema quality: unverified → excellent ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Licence: FSL-1.1-MIT functional
  • 1 Aug 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 11 Aug 2026 · Analysed npm/@mindstone/mcp-server-canary@0.0.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo mindstone/mcp-servers
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mindstone/mcp-servers/.github/workflows/release.yml@refs/heads/main
Rekor log index 1790522779
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:7c7bac4d920dcb96963f2ab86314d77ba7cd3fd7a813c9fc9dcbc39081ffa434ab84956190098946fd4147bddabb4496b6dc985ca2f6b3843bfd82c05
Dependencies 96 packages
Packages resolved 96
Stale 30
Tree resolution Complete
MCP tools · 1 exposed · ~58 tokens

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.

Tool Tokens
ping ~58

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.

NameTypeReqDescription
messagestringyesA short message to echo back. 1-200 chars.

No output schema declared.

No examples provided.