Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Open-source AI security agent: SAST, DAST, and policy-as-code over MCP.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"mythos-agent": {
"command": "npx",
"args": [
"-y",
"mythos-agent"
]
}
}
}ターミナルでこれを実行します
claude mcp add mythos-agent -- npx -y mythos-agentプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"mythos-agent": {
"command": "npx",
"args": [
"-y",
"mythos-agent"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"mythos-agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mythos-agent"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント mythos-agent で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(4.0.1)がレジストリに届いたのは7 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Apify MCP Server
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
English · 简体中文
mythos-agent AI code-review assistant for application security. Open-source. Reads your code, flags likely security issues, explains its reasoning, suggests fixes.
mythos-agent.com
Quick Start • How It Works • Commands • Hunt Mode • Variant Analysis • Integrations • Contributing • Vision • Roadmap
mythos-agent reviews your code the way a reviewer on a security-focused team would. It walks through likely issue patterns, checks for variants of known CVEs, ranks findings by confidence, and suggests fixes you can accept or reject. See VISION.md for the full framing.
For new contributors: the active 6-month working plan is in the pinned issue `[Roadmap] mythos-agent H1 2026 Goals`. Look for 🙋 markers to spot items where help is wanted. New here? See CONTRIBUTING.md for
good-first-issueguidance.
For security teams and EU CRA-compliant downstream manufacturers: see SECURITY.md for our vulnerability disclosure SLAs, docs/security/cra-stance.md for our EU CRA role declaration, docs/security/threat-model.md for our public threat model, and RELEASES.md for our versioning, LTS, and EOL policy. OpenSSF Best Practices Badge (Passing) submission targeted June 2026; releases are signed via Sigstore and ship with CycloneDX SBOMs for downstream Manufacturer compliance.
npx mythos-agent hunt
🔐 mythos-agent hunt — AI Code-Review Assistant
✔ Phase 1: Reconnaissance — 12 entry points, express, typescript, postgresql ✔ Phase 2: Hypothesis — 8 security hypotheses generated ✔ Phase 3: Analysis — 15 findings (semgrep, gitleaks, trivy, built-in), 22 false positives dismissed ✔ Phase 4: Reproduction — 2 finding chains, 3 reproductions
🧪 Security Hypotheses
[HIGH] HYPO-001 — Race condition: concurrent payment requests could double-charge src/payments.ts:45 (race-condition) [HIGH] HYPO-002 — Auth bypass: JWT token not validated after password change src/auth.ts:78 (auth-bypass)
📊 Confidence Summary
3 confirmed | 8 likely | 4 possible | 22 dismissed
⛓️ FINDING CHAINS
CRITICAL SQL Injection → Auth Bypass → Data Exfiltration ├── src/api/search.ts:45 — unsanitized input in SQL query ├── src/middleware/auth.ts:88 — JWT verification skippable └── src/api/export.ts:23 — bulk export has no ACL
🧪 Reproductions
SPX-0001 — SQL injection in search endpoint See repro steps in docs/reproductions/SPX-0001.md
Trust Score: 2.3/10 — critical issues found
# Install
npm install -g mythos-agent
mythos-agent scan
mythos-agent init mythos-agent hunt
mythos-agent variants CVE-2021-44228
mythos-agent ask "are there any auth bypasses?"
mythos-agent tools
mythos-agent combines three things no other open-source tool does together:
Instead of matching known patterns, the AI reasons about what COULD go wrong, generating hypotheses like "this transaction doesn't lock the row, potential race condition" or "this auth check uses string comparison, potential timing attack."
Given a known CVE, mythos-agent finds structurally similar but syntactically different code in your codebase. Same root cause, different location. This is how Google's Big Sleep found 20 real zero-days.
Every finding goes through a confidence pipeline:
Only findings that survive multiple stages are reported as "confirmed."
| Command | Description |
|---|---|
hunt [path] | Full autonomous multi-agent scan (Recon → Hypothesize → Analyze → Exploit) |
scan [path] | Standard scan (patterns + secrets + deps + IaC + AI) |
variants [cve-id] | Find variants of known CVEs in your codebase |
fix [path] | AI-generated patches with --apply |
ask [question] | Natural language security queries |
taint [path] | AI data flow / taint analysis |
watch | Continuous monitoring that scans on file save |
dashboard | Local web UI with charts and findings table |
report [path] | Export as terminal / JSON / HTML / SARIF |
policy | Policy-as-code with SOC2/HIPAA/PCI/OWASP compliance |
rules | Community rule pack registry (search/install/publish) |
tools | Check which external security tools are installed |
init | Setup wizard (Anthropic, OpenAI, Ollama, LM Studio) |
mythos-agent hunt runs the full multi-agent pipeline:
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Recon │ → │ Hypothesis │ → │ Analyze │ → │ Exploit │ │ Agent │ │ Agent │ │ Agent │ │ Agent │ ├──────────────┤ ├──────────────┤ ├──────────────┤ ├──────────────┤ │ Map entry │ │ Reason about │ │ All scanners │ │ Chain vulns │ │ points, auth │ │ what could │ │ + external │ │ + generate │ │ boundaries, │ │ go wrong per │ │ tools + AI │ │ PoC exploits │ │ data stores │ │ function │ │ verification │ │ │ └──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘
Find code in your project that has the same root cause as known CVEs:
# Search for Log4Shell-like patterns
mythos-agent variants CVE-2021-44228
mythos-agent variants --auto
The variant analyzer extracts the root cause pattern from the CVE (not the surface syntax) and searches your codebase for structurally similar code.
The Default scanners run on every mythos-agent scan. Experimental scanners are implemented + unit-tested classes that ship in the tarball but are not yet reachable from any CLI, HTTP, MCP, or agent entry point. They are tracked by KNOWN_EXPERIMENTAL in the wiring-invariant test.
| Category | What it finds | Rules | Status |
|---|---|---|---|
| Code patterns | SQLi, XSS, command injection, eval, SSRF, etc. | 25+ | Default |
| Framework rules | React, Next.js, Express, Django, Flask, Spring, Go | 27 | Default |
| Secrets | AWS, GitHub, Stripe, API keys, DB URLs, private keys + entropy | 22 | Default |
| Dependencies (SCA) | Known CVEs via OSV API (10 lockfile formats) | OSV | Default |
| IaC | Docker, Terraform, Kubernetes misconfigurations | 13 | Default |
| AI/LLM Security | Prompt injection, unsafe eval of AI output, cost attacks | 13 | Default |
| API Security | OWASP API Top 10: BOLA, mass assignment, broken auth | 12 | Default |
| Cloud Misconfig | AWS/Azure/GCP: public storage, wildcard IAM, open firewalls | 14 | Default |
| Security Headers | CSP, HSTS, X-Frame-Options, Referrer-Policy | 8 | Default |
| JWT | Algorithm, expiry, storage, revocation, audience | 9 | Default |
| Session | Fixation, expiry, cookie flags, localStorage tokens | 7 | Default |
| Business Logic | Negative amounts, coupon reuse, inventory races, role escalation | 6 | Default |
| Crypto Audit | Weak hashes, ECB mode, hardcoded keys, deprecated TLS | 11 | Default |
| Privacy/GDPR | PII handling, consent, data retention (GDPR article mapping) | 9 | Default |
| Race Conditions | TOCTOU, non-atomic ops, double-spend, missing transactions | 7 | Default |
| ReDoS | Catastrophic backtracking in regex (nested quantifiers, overlapping alternatives) | — | Default |
| Supply Chain | Typosquatting, dependency confusion, dangerous install scripts | 12 | Experimental |
| Zero Trust | Service trust, mTLS, network segmentation, IP-based auth | 8 | Experimental |
| GraphQL | Introspection, depth limit, field auth, batching | 8 | Experimental |
| WebSocket | Auth, origin check, message validation, broadcast XSS | 7 | Experimental |
| CORS | Origin reflection, credentials handling, substring bypass | 7 | Experimental |
| OAuth/OIDC | Missing state, no PKCE, implicit flow, client secret exposure | 7 | Experimental |
| SSTI | Jinja2, EJS, Handlebars, Pug, Nunjucks, Twig, Go templates | 7 | Experimental |
Additional experimental scanners (21 more, not yet wired into default scan)
SQL injection deep, XSS deep, NoSQL, command injection, deserialization, path traversal, open redirect, XXE, input validation, clickjacking, DNS rebinding, subdomain enumeration, dep confusion, environment variables, logging, error handling, cache, email, upload, memory safety, permissions.
Each exists as a class under src/scanner/ and has unit tests in src/scanner/__tests__/coverage-scanners.test.ts / new-scanners.test.ts, but is not invoked by any CLI command, HTTP API route, MCP handler, or agent pipeline. See KNOWN_EXPERIMENTAL in the wiring-invariant test for each scanner's deferral reason. Wiring one up follows the pattern of the HeadersScanner / JwtScanner / SessionScanner / BusinessLogicScanner commits on main.
Beyond the scanners above, mythos-agent ships complementary analyses (not counted in the scanner totals): call-graph + taint engine, DAST smart fuzzer, AI hypothesis agent, variant analysis, and git-history mining.
External tool integrations: Semgrep (30+ languages), Gitleaks (100+ patterns), Trivy (SCA + containers), Checkov (1000+ IaC policies), Nuclei (9000+ DAST templates)
| Platform | What |
|---|---|
| VS Code | Extension with inline diagnostics + one-click AI fix |
| GitHub Action | Scan on push/PR + SARIF upload to Code Scanning |
| PR Review Bot | Inline comments on vulnerable lines in pull requests |
| Dashboard | Local web U
冒頭だけを表示しています。続きはリポジトリで読めます