Mcp Empty Public

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

Minimal streamable HTTP MCP server used for owned-account registry connectivity tests.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A minimal remote MCP server used to test registry connectivity and publishing from its owner's account; it offers no tools.

What you can do
The server is described as a minimal streamable HTTP MCP server with no listed tools, so an assistant gains no callable capabilities from connecting to it. Its stated purpose is validating registry publishing and owned-account connectivity tests. It is a connectivity check rather than a working toolset.
When to use it
Only useful if you want to confirm that an MCP client can reach a remote streamable HTTP endpoint or that registry publishing works for this account. It is not intended for real tasks.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared. Network access to the endpoint is needed.
Before you install
No credentials are requested and no tools are listed, so there is little to act on, but the endpoint is third-party operated and its behavior may change without notice. Do not rely on it for anything beyond a connectivity check.

Installation

In SourceWeft

  1. Open Mcp Empty Public 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%2Fmcp-empty-public/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": {
    "empty-public": {
      "type": "http",
      "url": "https://bintool.brkd.no/anything/mcp-empty-public"
    }
  }
}

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.1LatestSep 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.