← all advisories

Vulnerability Disclosure Policy

Still OS Digital Holdings LLC · Still OS MCP Supply-Chain Security Research

Scope

We research the Model Context Protocol (MCP) agent-tool ecosystem — published MCP servers and the npm/registry supply chain beneath them. Findings are reportable when a vulnerability class is reachable through a tool argument an LLM supplies.

How we disclose

We notify the maintainer first, privately where a channel exists, on a standard 90-day coordinated-disclosure timeline. Where no security contact or private reporting exists, we open a public issue carrying no technical detail to request a private channel. No weaponized reproduction is published before a fixed version ships. Confirmed findings are filed with MITRE and published here, with the affected component and public references so anyone can verify them from the package's own source.

Safe harbor & good faith

Our findings are exposure, not accusation: a published CVE is a coordinated-disclosure finding, never an assertion of intent or wrongdoing by any maintainer. We never exfiltrate data, never run a reproduction against infrastructure we do not own, and withhold working exploits under coordinated disclosure.

Report a vulnerability to us, or dispute a finding

Security contact: security@stillosdigitalholdings.com · disclosure form · machine-readable advisories in CSAF 2.0.

Still OS Digital Holdings LLC · Wyoming · Still OS MCP Supply-Chain Security Research.