Open Registry Poc

io.github.NOTTIBOY137Published by GitHub account NOTTIBOY137v1.0.0Updated Oct 24, 2026

PoC: Open Registry supply chain — unvetted server listing (security research)

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A proof-of-concept npm MCP server published as a supply-chain security research listing; no tools, instructions or README are documented.

What you can do
  • The registry entry describes it only as a proof-of-concept for an open registry supply chain, explicitly labelled an unvetted server listing for security research.
  • No tools are listed in the manifest, and the server provides no instructions or README, so what an assistant could actually do with it is undocumented.
  • It runs as a local stdio process on the user's machine and declares no authentication, environment variables or headers.
When to use it
Only relevant if you are studying MCP registry supply-chain risks or testing how unvetted listings appear in catalogs. It offers no documented capability for everyday assistant work, so there is no practical reason to add it otherwise.
Requirements
A local runtime able to run the npm package @nottiboy1337/mcp-open-registry-poc over stdio, on a desktop machine. No accounts, API keys, environment variables or headers are declared.
Before you install
The listing itself states it is unvetted and published as security research, so treat the package as untrusted code that would execute locally with your user's permissions. No tools, source review or documentation are available to judge what it does; install only in an isolated environment if at all.

Installation

In SourceWeft

  1. Open Open Registry Poc 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

This repository has no README.

Tools

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

Version history

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