Readme Canary

io.github.brkd-h1Published by GitHub account brkd-h1v0.0.2Updated Oct 24, 2026

Security research canary remote MCP server for owned-account testing.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A minimal remote MCP server published as a security research canary and registry-publishing test, with no documented tools or capabilities.

What you can do
The registry description calls it a security research canary remote MCP server for owned-account testing. The README describes it as a minimal Model Context Protocol server used to validate registry publishing from the provider's account. No tools are listed in the manifest, and no instructions or usage sections describe any capability. It appears to exist to test publishing and connectivity rather than to give an assistant working tools.
When to use it
Only if you are the publishing account testing MCP registry publication or a canary endpoint for owned-account security research. It is not intended for general assistant tasks, since no tools or capabilities are documented.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared.
Before you install
No authentication is declared, so treat anything sent to the endpoint as unauthenticated. It is described as a research canary for owned-account testing; do not point it at accounts or data you do not own, and expect no useful tooling.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.brkd-h1%2Freadme-canary/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "readme-canary": {
      "type": "http",
      "url": "https://bintool.brkd.no/anything/mcp-brkd-canary"
    }
  }
}

README

mcp-empty-public

Minimal Model Context Protocol server used to validate registry publishing from this account.

Source: README.md at commit 1cd8956

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.0.2LatestSep 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 daysRequired25 pts

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

  • Auth declaredRequired10 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.