TOPY.AI · AI CSO

ai.topyPublished by topy.aiOfficial publisherv0.1.0Updated Nov 5, 2026

Founders' AI CSO: vulnerabilities, dependencies, secrets, verified-site checks, threat model, fixes.

The publisher's own server: TOPY.AI · AI CEO

Overview

AI-generated overview

TOPY.AI AI CSO gives a coding agent security-chief skills: CVE and dependency checks, secret scanning, verified-site web checks, threat models and incident…

What you can do
  • Check exposure to named CVEs, lockfile dependencies, end-of-life runtimes and packages before install
  • Scan code for secrets, unsafe patterns, and build STRIDE threat models with OWASP ASVS checklists
  • Verify domains, grade HTTP headers, cookies and TLS, and run safe scans of verified sites
  • Vet skills, plugins and MCP servers before trusting them, and audit your own MCP registry
  • Record incidents, produce tiered fix plans for a person to apply, and send a weekly security report
When to use it
Useful for a small team or solo founder who wants an agent to keep a standing security watch: daily CVE and end-of-life alerts, pre-ship secret and code checks, and a weekly report. Also suited to vetting third-party skills and MCP servers before installing them.
Requirements
A TOPY.AI account with OAuth, or a TOPY_API_KEY (or a one-time login via the npm package). Remote endpoint at topy.ai, or the local stdio package @topy-ai/cso-mcp, which forwards to it. Host checks and public checks need a person on OneMan with host consent. Network access required.
Before you install
OAuth grants access to your TOPY.AI account; only accounts owning the OneMan operation see its findings. The server reads code, git history and build output to find secrets, and findings go to TOPY.AI. It states it never changes servers, firewalls or sites and never prints secrets, but fix plans and scans should still be reviewed by a person.

Installation

In SourceWeft

  1. Open TOPY.AI · AI CSO in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.topy%2Fcso/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "topy-ai-ai-cso": {
      "type": "http",
      "url": "https://topy.ai/mcp/cso"
    }
  }
}

README

[TOPY AI CSO]

TOPY AI CSO Skills

19 skills that make your coding agent a small company's AI CSO: new CVEs and end-of-life dates for everything you run, no secrets in code, headers, TLS and safe scans of the domains you have verified, every skill and MCP server vetted before it is trusted, incident timelines and a weekly security report to the founder and the CEO — on the TOPY.AI CSO MCP server.

[npm] [MIT License] [MCP]


The AI CSO is goal-first. It keeps five standing goals — no open critical exposure (anything on CISA KEV or critical with a fix is fixed within days), zero secrets in code, verified-only active checks, nothing trusted unvetted (every new skill, MCP server and package checked first) and every incident with a timeline — and every skill below exists to move one of them.

  • Core (topy-ai-cso): connect, first setup (inventory, domain verification, host consent), the CSO's goals, the daily watch.
  • Vulnerabilities: are we affected by this CVE, dependencies and supply chain, end of life, vetting a package before install.
  • Code: secrets (rotate first, then remove), unsafe code patterns, a STRIDE threat model and the OWASP ASVS checklist.
  • Web: domain verification, headers and TLS, a safe scan of a verified site.
  • Agents: vet a skill or MCP server before it is installed (the App Factory gate), and audit your own MCP server.
  • Response: incident timelines, a fix plan with fix-risk tiers T1–T4, the weekly security report.

The safety model comes from Maggie Security and does not bend: the CSO never changes a server, firewall or website (fix and protection plans are for a person to review and apply), never scans a domain you have not verified, reads a server only after you grant consent yourself, by your own approval in the chat (an agent cannot), leaves checks of sites you don't control to a person (never a routine), never uses offensive techniques and never prints a secret. Changes take two calls — a preview, then your yes.

Install

sh
npx @topy-ai/cso-skills install                  # this project, for the agents set up herenpx @topy-ai/cso-skills install -g --mcp         # your user, plus the MCP servernpx @topy-ai/cso-skills install --category vulnerabilities,webnpx @topy-ai/cso-skills list

Claude Code plugins: /plugin marketplace add TOPY-AI-LTD/TOPY-AI-CSO-Skills, then /plugin install topy-ai-cso-all@topy-ai-cso. Codex: codex plugin marketplace add TOPY-AI-LTD/TOPY-AI-CSO-Skills. Pi: pi install npm:@topy-ai/cso-skills. See the installer README.

Connect TOPY.AI

https://topy.ai/mcp/cso — OAuth with your TOPY.AI account (the same one as the AI CEO, CFO and COO). Only the accounts that own the OneMan operation see its findings.

ClientHow
Claude, ChatGPT (web, desktop)custom connector https://topy.ai/mcp/cso
Claude Codeclaude mcp add --transport http topy-cso https://topy.ai/mcp/cso
Codexcodex mcp add topy-cso --url https://topy.ai/mcp/cso
Clients that only start a commandnpx -y @topy-ai/cso-mcp after npx @topy-ai/cso-mcp login
Terminal and scriptsnpm i -g @topy-ai/cso-cli && cso-cli login

Server checks (host-quick, host-audit) and passive checks of sites you don't control (public-check) are not on topy.ai: they need a person on OneMan, with host consent granted by the person's own approval in the chat.

How the skills fit together

topy-cso-connect ─▶ topy-cso-setup (inventory · domain verify · consent) ─▶ topy-cso-goals        │   daily 06:17: topy-cso-daily-watch ─▶ topy-cso-cve-response ─▶ topy-cso-incident ─▶ topy-cso-fix-plan        │                               topy-cso-dependencies · topy-cso-end-of-life   weekly Mon 07:23: topy-cso-weekly-report ─▶ the founder (email) and the CEO        │   before code ships: topy-cso-secrets · topy-cso-code-scan · topy-cso-threat-model   web (verified domains): topy-cso-domain-verify ─▶ topy-cso-web-checks ─▶ topy-cso-web-scan   before you trust it: topy-cso-package-vet · topy-cso-vet-skill · topy-cso-mcp-audit

Try: "Anything new I should worry about?", "Are we affected by CVE-2026-…?", "Did a key leak?", "Is this MCP server safe to install?", "Send the weekly security report"

Packages

PackageWhat it is
@topy-ai/cso-skillsThis installer (Claude Code, Codex, Pi, Cursor, Gemini CLI, …)
@topy-ai/cso-mcpThe CSO MCP server as a local stdio server (forwards to https://topy.ai/mcp/cso)
@topy-ai/cso-cliThe AI CSO on the command line

Repository structure

plugins/  topy-ai-cso/                   core skills + .mcp.json (Claude Code) and mcp.json (Codex)  topy-ai-cso-vulnerabilities/   topy-ai-cso-code/   topy-ai-cso-web/  topy-ai-cso-agents/            topy-ai-cso-response/  topy-ai-cso-all/               bundle that depends on all six.claude-plugin/marketplace.json     Claude Code marketplace.agents/plugins/marketplace.json    Codex marketplaceskills.json                         machine-readable cataloguepackages/skills/                    the @topy-ai/cso-skills installer

The skills are generated from a source catalogue kept next to TOPY.AI's MCP server; the build checks every tool a skill names against the CSO server's tool list. Please open an issue rather than editing a SKILL.md.

License

MIT © TOPY AI LTD. Privacy: topy.ai/privacy.

Skills

19 skills in 6 plugins, plus the topy-ai-cso-all bundle. Generated from the source catalogue: please open an issue rather than editing a SKILL.md.

AI CSO core (MCP) · topy-ai-cso

SkillTierWhat it does
topy-cso-connectcoreConnect the TOPY CSO MCP server and check what applies: the project's stack, verified domains, granted hosts, tools and feeds.
topy-cso-daily-watchcoreEvery morning: new CVEs, advisories and end-of-life dates for everything the company runs, matched to the stack — quiet unless something new needs a person.
topy-cso-goalscoreThe AI CSO's standing goals and its status report for the CEO: open critical exposure, secrets in code, verified-only checks, vetted skills and MCP servers, incident timelines.
topy-cso-setupcoreFirst run for a new company or site: inventory the stack, verify each domain you own, and explain host consent — so every later check is allowed and complete.

Vulnerabilities & supply chain · topy-ai-cso-vulnerabilities

SkillTierWhat it does
topy-cso-cve-responseconnectedA named CVE or advisory: are we affected, where, how urgent, and the response plan — with an incident timeline from start to close.
topy-cso-dependenciesconnectedKnown vulnerabilities in every lockfile ecosystem and in JavaScript copied into the site, prioritised, with the fixed versions.
topy-cso-end-of-lifeconnectedRuntimes, databases, web servers and operating systems that stopped (or will soon stop) getting security fixes, and what to upgrade to.
topy-cso-package-vetconnectedBefore adding a package: known vulnerabilities and malicious-package reports for that exact version, and a clear install / pin / don't install.

Code & secrets · topy-ai-cso-code

SkillTierWhat it does
topy-cso-code-scanconnectedUnsafe code patterns before they ship — injection, unsafe deserialisation, personal data in logs, weak crypto — with the safe pattern for each.
topy-cso-secretsconnectedKeys, tokens and passwords in the code, its git history and the build output — and the rotate-first fix for each.
topy-cso-threat-modelconnectedA STRIDE threat model of the system and an OWASP ASVS checklist filled from the findings — what could go wrong and how far we meet the standard.

Web surface · topy-ai-cso-web

SkillTierWhat it does
topy-cso-domain-verifyconnectedProve the company controls a domain (DNS TXT record or a token file) before any active check — the CSO never scans a site that isn't verified.
topy-cso-web-checksconnectedGrade a verified site's HTTP security headers and cookies (A+ to F) and its TLS (protocols, certificate trust and expiry), with the exact fix for each.
topy-cso-web-scanconnectedA safe, rate-limited vulnerability scan (known flaws, exposed files, misconfigurations) of a site the company has verified — never exploitation.

Agent & MCP security · topy-ai-cso-agents

SkillTierWhat it does
topy-cso-mcp-auditconnectedOWASP MCP checks on the company's own MCP tool registry: read-only hints, destructive tools behind confirmation, scopes, audit logging and hosts it may call.
topy-cso-vet-skillconnectedBefore a skill, plugin or MCP server is installed or published: prompt-injection, data exfiltration, over-broad permissions and risky tools — the App Factory security gate.

Response & reporting · topy-ai-cso-response

SkillTierWhat it does
topy-cso-fix-planconnectedTurn the findings into a reviewed runbook — each action tagged T1 (batch-safe) to T4 (stage first) — that a person reviews and runs. The CSO never applies it.
topy-cso-incidentconnectedRecord a security incident or CVE response from start to close — what happened, every step and who did it — so nothing is lost and the report writes itself.
topy-cso-weekly-reportconnectedEvery Monday: what is open by priority, what was fixed, what changed in the stack, and at most three actions — for the Founder by email and for the CEO.

Source: README.md at commit 40cbf4e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

Other Topy integrations