Open Registry Poc
Study how unvetted MCP registry listings can affect supply chain trust—not to run production agent tooling.
Overview
open-registry-poc is an MCP server for the Ship phase that demonstrates unvetted Open Registry supply-chain listing risk for security research only.
What is this MCP server?
- Explicit PoC: Open Registry supply chain with unvetted server listing
- Security research focus from NOTTIBOY137/mcp-open-registry-poc
- stdio npm package @nottiboy1337/mcp-open-registry-poc version 1.0.0
- Intended for reproducing registry-risk scenarios, not product features
- Contrast with curated directories that vet MCP entries before install
- npm identifier @nottiboy1337/mcp-open-registry-poc
- Transport: stdio
What problem does it solve?
Agents can install MCP servers from open registries without understanding that listings may be unvetted or misleading.
Who is it for?
Security researchers and MCP maintainers documenting open-registry risks and education demos.
Skip if: Solo builders wiring everyday product integrations or anyone seeking vetted production MCP tools.
What do I get? / Deliverables
Researchers can reproduce supply-chain listing scenarios to reason about registry trust policies and safer install workflows.
- Reproducible open-registry listing scenario for security writeups or demos
- Evidence for why curated MCP directories and pinning matter
Recommended MCP Servers
Journey fit
How it compares
Intentional supply-chain PoC, not a curated marketplace entry you should ship with.
Common Questions / FAQ
Who is open-registry-poc for?
Security researchers and developers studying MCP registry supply-chain risks, not indie builders looking for a normal integration.
When should I use open-registry-poc?
Use it in controlled lab setups when you explain or test how unvetted server listings affect agent install trust—not in production agent configs.
How do I add open-registry-poc to my agent?
Only in an isolated research environment: install @nottiboy1337/mcp-open-registry-poc via npm stdio per the GitHub repo, never alongside production secrets or customer data.