@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.
Maintainers
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
