Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Founders' AI CSO: vulnerabilities, dependencies, secrets, verified-site checks, threat model, fixes.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
TOPY_API_KEY비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://topy.ai/mcp/csoClaude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"cso": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cso-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
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-mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"cso": {
"url": "https://topy.ai/mcp/cso"
}
}
}프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"cso": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cso-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"cso": {
"type": "http",
"url": "https://topy.ai/mcp/cso"
}
}
}프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"cso": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@topy-ai/cso-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://topy.ai/mcp/cso메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 topy.ai 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: TOPY_API_KEY
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0)은 10일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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. |