Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Founders' AI CSO: vulnerabilities, dependencies, secrets, verified-site checks, threat model, fixes.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
TOPY_API_KEYLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://topy.ai/mcp/csoAbre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"cso": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cso-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add --transport http cso https://topy.ai/mcp/csoclaude mcp add cso --env TOPY_API_KEY=your-value -- npx -y @topy-ai/cso-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"cso": {
"url": "https://topy.ai/mcp/cso"
}
}
}Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"cso": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cso-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"cso": {
"type": "http",
"url": "https://topy.ai/mcp/cso"
}
}
}Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"cso": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@topy-ai/cso-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://topy.ai/mcp/csoLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con el dominio topy.ai (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: TOPY_API_KEY
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
El repo de GitHub cambió por última vez –, y la última versión (0.1.0) llegó al registro hace 10 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, topo^alpin
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
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.
topy-ai-cso): connect, first setup (inventory, domain verification, host consent), the CSO's goals, the daily watch.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.
npx @topy-ai/cso-skills install # this project, for the agents set up here
npx @topy-ai/cso-skills install -g --mcp # your user, plus the MCP server npx @topy-ai/cso-skills install --category vulnerabilities,web npx @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.
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.
| Client | How |
|---|---|
| Claude, ChatGPT (web, desktop) | custom connector https://topy.ai/mcp/cso |
| Claude Code | claude mcp add --transport http topy-cso https://topy.ai/mcp/cso |
| Codex | codex mcp add topy-cso --url https://topy.ai/mcp/cso |
| Clients that only start a command | npx -y @topy-ai/cso-mcp after npx @topy-ai/cso-mcp login |
| Terminal and scripts | npm 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.
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"*
| Package | What it is |
|---|---|
@topy-ai/cso-skills | This installer (Claude Code, Codex, Pi, Cursor, Gemini CLI, …) |
@topy-ai/cso-mcp | The CSO MCP server as a local stdio server (forwards to https://topy.ai/mcp/cso) |
@topy-ai/cso-cli | The AI CSO on the command line |
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 marketplace skills.json machine-readable catalogue packages/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.
MIT © TOPY AI LTD. Privacy: topy.ai/privacy.
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.
topy-ai-cso| Skill | Tier | What it does |
|---|---|---|
topy-cso-connect | core | Connect the TOPY CSO MCP server and check what applies: the project's stack, verified domains, granted hosts, tools and feeds. |
topy-cso-daily-watch | core | Every 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-goals | core | The 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-setup | core | First 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. |
topy-ai-cso-vulnerabilities| Skill | Tier | What it does |
|---|---|---|
topy-cso-cve-response | connected | A named CVE or advisory: are we affected, where, how urgent, and the response plan — with an incident timeline from start to close. |
topy-cso-dependencies | connected | Known vulnerabilities in every lockfile ecosystem and in JavaScript copied into the site, prioritised, with the fixed versions. |
topy-cso-end-of-life | connected | Runtimes, databases, web servers and operating systems that stopped (or will soon stop) getting security fixes, and what to upgrade to. |
topy-cso-package-vet | connected | Before adding a package: known vulnerabilities and malicious-package reports for that exact version, and a clear install / pin / don't install. |
topy-ai-cso-code| Skill | Tier | What it does |
|---|---|---|
topy-cso-code-scan | connected | Unsafe code patterns before they ship — injection, unsafe deserialisation, personal data in logs, weak crypto — with the safe pattern for each. |
topy-cso-secrets | connected | Keys, tokens and passwords in the code, its git history and the build output — and the rotate-first fix for each. |
topy-cso-threat-model | connected | A 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. |
topy-ai-cso-web| Skill | Tier | What it does |
|---|---|---|
topy-cso-domain-verify | connected | Prove 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-checks | connected | Grade 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-scan | connected | A safe, rate-limited vulnerability scan (known flaws, exposed files, misconfigurations) of a site the company has verified — never exploitation. |
topy-ai-cso-agents| Skill | Tier | What it does |
|---|---|---|
topy-cso-mcp-audit | connected | OWASP 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-skill | connected | Before 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. |
topy-ai-cso-response| Skill | Tier | What it does |
|---|---|---|
topy-cso-fix-plan | connected | Turn 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-incident | connected | Record 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-report | connected | Every 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. |