npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@topy-ai/cso-mcp

v0.1.0

Published

TOPY.AI's AI CSO as a local stdio MCP server, for MCP clients that only run local servers. Forwards to https://topy.ai/mcp/cso.

Readme

@topy-ai/cso-mcp

TOPY.AI's AI CSO as a local stdio MCP server, for MCP clients that only run local servers. Every message goes to https://topy.ai/mcp/cso with your TOPY sign-in. Clients with remote MCP can use that URL directly.

{ "mcpServers": { "topy-cso": { "command": "npx", "args": ["-y", "@topy-ai/cso-mcp"] } } }

Sign in once with npx @topy-ai/cso-mcp login (shared with cso-cli, cfo-cli and ceo-cli), or set TOPY_API_KEY (Dashboard → API keys).

Tools

  • Status and reports (reads): cso_status_report (open criticals, risks and asks for the CEO), cso_doctor (what applies: tools, feeds, verified domains, consents), cso_scan (one full check), cso_report, cso_ledger, cso_inventory, cso_uptime_status.
  • Vulnerabilities and supply chain: cso_vuln_watch (OSV, KEV, EPSS), cso_osv_query, cso_deps, cso_eol_watch.
  • Code and secrets: cso_secrets, cso_code_scan.
  • Web surface (verified domains only): cso_headers, cso_tls.
  • Standards and agents: cso_checklist (OWASP ASVS), cso_threat_model (STRIDE), cso_skills_scan, cso_mcp_self_check.
  • Changes (preview first): cso_domain_verify (prove you control a domain), cso_web_scan (a safe scan of a verified site), cso_fix_plan (a runbook you apply yourself), cso_incident, cso_report_send (the daily or weekly security report).

Writes take two calls: a preview, then the same call with confirm: true after you agree. The CSO never changes a server and never scans a site you haven't verified. Projects are names on OneMan (default oneman). Prompts (workflows) cover the daily watch, the weekly report, the release gate, verifying a domain and incidents.

MIT · topy.ai/developers