Agent Canary

io.github.DorianChnPublished by GitHub account DorianChnv1.2.7Updated Oct 24, 2026

Free V1: inert MCP decoys and canary tokens detect AI-agent compromise signals. Local stdio server.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Agent Canary is a local stdio MCP server that provides inert decoy tools and canary tokens to surface signs of AI-agent compromise.

What you can do
  • Supplies inert MCP decoy tools that an assistant can see and call.
  • Places canary tokens intended to reveal when an agent has been compromised.
  • Runs locally over stdio as a free V1 release.
  • No tool list, instructions or README is published, so the exact tool set is not documented.
When to use it
Worth considering when you want a low-cost way to add tripwires around an AI agent setup and watch for signs that it has been tampered with or misused.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, not executable in a web context. No packages, environment variables, headers or authentication are declared.
Before you install
The decoys are described as inert, but no tool list or documentation is provided, so what the server actually exposes cannot be verified before installing. Review the source before use.

Installation

In SourceWeft

  1. Open Agent 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.

Tools

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

Version history

2
  1. v1.2.7LatestSep 23, 2026
  2. v0.8.0Sep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.