Canary

io.github.mindstonePublished by GitHub account mindstonev0.0.4Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Mindstone's internal release-pipeline test connector exposing a single ping tool that echoes a message back; explicitly not intended for real use.

What you can do
  • Echo a short message back as a pong response (single ping tool)
  • Nothing else: no external dependencies, no authentication, no bridge
When to use it
Only for validating Mindstone's own release pipeline end to end. It is not meant for real workflows, so there is no practical reason for an end user to install it.
Requirements
Runs locally over stdio, typically started with npx from the npm package. No environment variables, headers, accounts or API keys are required.
Before you install
The README states it is a canary for internal release testing, deliberately versioned 0.0.x, and that it should not be depended on for any real workflow. Installing it adds no useful capability.

Installation

In SourceWeft

  1. Open Canary in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@mindstone/mcp-server-canary

Mindstone's internal release-pipeline test connector — not for use. It exists only to validate the rebel-oss release pipeline end-to-end. Single ping tool; no external dependencies, no auth, no bridge.

One-click install

[Add to Cursor] [Add to VS Code] [Add to VS Code Insiders]

No required environment variables — the install completes without prompts.

Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Canary)
json
{  "mcpServers": {    "Canary": {      "command": "npx",      "args": [        "-y",        "@mindstone/mcp-server-canary"      ],      "env": {}    }  }}

Why this exists

Releasing a real connector for the first time through a brand-new pipeline (Trusted Publishing, GitHub Actions, mcp-publisher, registry sync, host-app catalog) couples two unknowns: the pipeline correctness AND the connector correctness. The canary decouples them — it exercises every step of the pipeline with a tool whose only behaviour is ping → pong v3: <message>.

Once the pipeline has proven itself stable on the canary, real connectors can adopt the same path without piggy-backing on infrastructure debugging.

See docs/plans/260525_oss_release_automation.md (Mindstone-internal) for the full design.

Tools

ping

Echo a message back wrapped as pong v3: <message>.

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

Example:

json
{  "tool": "ping",  "arguments": { "message": "hello" }}

Response:

pong v3: hello

Use locally

bash
npx -y @mindstone/mcp-server-canary

This starts the server on stdio. Most MCP hosts will spawn this for you when you add @mindstone/mcp-server-canary as a stdio MCP server.

Status

Pre-1.0 — this is the canary. Versions are stamped 0.0.x deliberately. Do not depend on this connector for any real workflow; its only purpose is to exercise the release machinery.

Source: connectors/canary/README.md at commit 22c4611

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.4LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.