[](https://security-recipes.ai/)
[](https://security-recipes.ai/cve-database/)
[](https://security-recipes.ai/mcp-servers/)
[](https://security-recipes.ai/docs/security-health-action/)
[](https://security-recipes.ai/llms.txt)
[](https://mcpservers.org/servers/security-recipes-ai-mcp-servers)
# security-recipes.ai
**Search CVEs. Remediate vulnerabilities with AI agents.** Sourced facts stay
sourced, remediation stays bounded, and every plan carries verification,
rollback, and stop conditions — the live site's contract, and this repo's.
[security-recipes.ai](https://security-recipes.ai/) is an Eleventy site for
sourced CVE intelligence and evidence-gated vulnerability remediation that AI
agents can consume without inheriting deployment or production authority.
The project is intentionally narrow:
- a complete rolling Medium/High/Critical CVE database,
- evidence-qualified canonical CVE remediation records,
- practical security remediation recipes,
- prompt and rules-file examples,
- agent setup guides,
- MCP integration patterns,
- an optional read-only MCP server for recipe search and approved upstream MCP
context,
- a [reusable GitHub Action](https://security-recipes.ai/docs/security-health-action/)
that turns this guidance into toggleable CI health checks.
It is not a scanner, ticketing system, SOAR platform, deployment tool, or custom
security toolkit. Existing security tools should produce the findings; this
site helps agents use the right remediation context and stop at the right time.
Start with the live [CVE Database](https://security-recipes.ai/cve-database/)
for an exact vulnerability or the
[AI Vulnerability Remediation Playbooks](https://security-recipes.ai/security-remediation/)
for the evidence-to-patch workflow. Agent-specific guides cover
[Codex](https://security-recipes.ai/codex/),
[Claude Code](https://security-recipes.ai/claude/),
[Cursor](https://security-recipes.ai/cursor/),
[GitHub Copilot](https://security-recipes.ai/github_copilot/),
[Devin](https://security-recipes.ai/devin/),
[Shiba Studio](https://security-recipes.ai/agents/#shiba-studio),
[Hermes Desktop](https://security-recipes.ai/agents/#hermes-desktop), and
[OpenClaw](https://security-recipes.ai/agents/#openclaw).
The [Visual Guide](https://security-recipes.ai/how-to-use/) shows the complete
path from source qualification and search discovery to a bounded plan, proof,
rollback, and human review.
For the distinct problem of securing an agent system's identities, tools,
connectors, context, memory, runtime, and recovery controls, use
[AI Agent Security](https://security-recipes.ai/agentic-security/).
## Current product and workflow
### Qualified search discovery
The complete catalog remains searchable, while public canonical CVE pages stay
limited to reviewed or evidence-qualified records. Those pages ship unique
search metadata, server-rendered core facts and affected-version evidence, one
remediation authority (stable reviewed guidance first, otherwise complete
source-linked AI enrichment), a short approval-gated AI implementation prompt,
canonical URLs, breadcrumbs, and `Article`/`TechArticle` structured data. The CVE database
describes the catalog as a `Dataset`; the remediation pillar exposes its visible
seven-step workflow as a `HowTo`. Year-partitioned CVE sitemaps contain only
indexable canonical routes, and the build fails when sitemap parity, canonical
ownership, crawl reachability, metadata limits, or same-origin links drift.
Indexability is also withheld from mass-templated recipe children. The 72
development code-hygiene recipes and 39 generated compliance-framework recipes
remain browsable from their canonical hubs with `noindex,follow` while they
share a common method. A bounded rendered-body similarity gate prevents a child
from re-entering sitemaps until its evidence, examples, and tests are materially
distinct. The hubs remain indexable and carry the shared discovery context.
After an SEO-bearing release, the public revision must match the merge commit
before sitemap submission or URL inspection. The
[Caddy deployment guide](https://github.com/stevologic/security-recipes.ai/blob/HEAD/README.caddy-deploy.md#search-discovery-after-an-seo-release)
documents the DNS-verified Search Console handoff, priority live-URL checks,
sitemap submission, indexing requests, and query monitoring. Submission is a
discovery hint; it does not guarantee indexing or a particular ranking.
The remediation pillar also records a public repository example for
[CVE-2026-13149 in `brace-expansion`](https://security-recipes.ai/security-remediation/#real-repository-case-study-cve-2026-13149-in-brace-expansion).
It ties the dependency-only change to the
[reviewed pull request](https://github.com/stevologic/security-recipes.ai/pull/89),
tests, advisory evidence, and recovery path while explicitly separating the
same PR's unrelated Fail2Ban work.
| CVE search to canonical record | CVE evidence to bounded agent plan |
| --- | --- |
|  |  |
| Proof and human review | Read-only MCP context |
|  |  |
## What this project is for
AI coding agents can help close security findings when their work is bounded:
one finding, one recipe, one reviewed output.
security-recipes.ai helps teams answer:
- Which recipe matches this finding?
- Which prompt should the agent use?
- Where do I put the instructions for Copilot, Claude, Cursor, Codex, or Devin?
- Which MCP servers should the agent read for advisory, scanner, repository, or
runbook context?
- What should the PR or triage note include before a reviewer trusts it?
## What ships
- Eleventy documentation site (fast static builds, no Go toolchain).
- CVE-first observatory home page and data-first CVE database.
- Recipe hubs for dependency, SAST, sensitive-data, base-image, CVE, and
default-hardening remediation.
- CVE intelligence intake policy, prompt, fixtures, and evaluator for routing
advisory signals before an agent patches.
- A complete rolling ten-year Medium/High/Critical CVE catalog composed from
integrity-verified NVD JSON 2.0 feeds, CISA KEV metadata, and every applicable
vetted remediation archetype. Only reviewed `stable` Markdown pages override
that conservative baseline.
- An integrity-hashed search allowlist that publishes canonical CVE pages only
for reviewed stable Markdown or AI enrichment that passes the deterministic
recipe-ready evidence contract. The full database remains searchable even
when a record is not eligible for search indexing.
- A versioned seven-phase agentic change contract for every catalog CVE:
discover, assess, mitigate, remediate, verify, rollback, and triage. Each
action declares likely file targets, mutation and approval boundaries,
required evidence, outputs, and failure behavior without guessing a patch or
fixed version.
- A structured compliance library spanning 39 security, privacy, assurance,
resilience, and software-supply-chain frameworks without reproducing
licensed control text. Its framework hub is the search surface; templated
child assessments remain `noindex,follow` until differentiated.
- A 72-recipe code-hygiene library covering cross-language and ecosystem-
specific audit, remediation, verification, and stop-condition workflows.
Its development children remain `noindex,follow` while their bodies share a
generated template.
- Recipes with existing prompt collections preserved.
- Agent setup guides for GitHub Copilot, Claude, Cursor, Codex, and Devin.
- MCP integration guidance for public and organization-approved security data
sources.
- Optional read-only FastMCP server in `mcp_server.py` for recipe search,
retrieval, and opt-in upstream MCP context.
- Docker and Docker Compose configuration for local or droplet hosting.
- Helper scripts for site maintenance, validation, imports, and deployment.
## Repository map
| Path | Purpose |
| --- | --- |
| `content/` | Recipes, documentation, remediation guides, and agent setup pages. |
| `eleventy.config.js` | Site build configuration (permalinks, feeds, tag pages). |
| `_includes/` | Page layouts: docs chrome and the standalone home page. |
| `lib/` | Build modules: shortcode ports, JSON feed builders, SEO head. |
| `assets/` | Site CSS and JavaScript for the recipe browser, navigation, and helper tools. |
| `static/` | Images, logos, schemas, and static assets. |
| `static/api/cve-catalog/` | Complete sharded CVE catalog, year-partitioned machine index, compressed browser-search index, provenance manifest, and archetypes. |
| `data/cve/` | Human-reviewed remediation archetypes, deterministic AI-enrichment cache, and generated-recipe ownership ledger. |
| `data/compliance-frameworks/` | Structured compliance-framework catalog and source registry. |
| `data/code-hygiene/` | Structured code-hygiene catalog, source registry, and routing fixtures. |
| `docs/` | Repository documentation and legacy screenshot assets; current README and visual-guide images live in `static/images/`. |
| `mcp_server.py` | Optional read-only MCP server for recipe search and approved upstream MCP context. |
| `mcp-server.toml.example` | MCP server configuration template. |
| `Dockerfile` | Site image. |
| `Dockerfile.mcp-server` | Optional MCP server image. |
| `docker-compose.yml` | Production-style local stack. |
| `scripts/` | Helper scripts for maintenance and deployment. |
## Core content areas
- **[CVE Database](https://security-recipes.ai/cve-database/)**: sourced CVE
intelligence, affected-version evidence, and canonical remediation records.
- **[AI Vulnerability Remediation](https://security-recipes.ai/security-remediation/)**:
evidence-gated playbooks from one finding to a reviewed patch or triage note.
- **[AI Agent Security](https://security-recipes.ai/agentic-security/)**:
threat modeling, production baselines, source boundaries, control routing,
evidence, and incident readiness for the AI-agent system itself.
- **[Quick Start](https://security-recipes.ai/quickstart/)**: one finding to one
reviewed PR or triage note.
- **[AI Agent Comparison](https://security-recipes.ai/agents/)**: verified
operating modes, native instructions, expected artifacts, prerequisites, and
review gates for Copilot, Claude Code, Cursor, Codex, and Devin.
- **[Recipes](https://security-recipes.ai/recipes/)**: reusable prompts,
instructions, rules, skills, and review checklists.
- **[MCP Integration](https://security-recipes.ai/mcp-servers/)**: how to connect
security context safely.
- **[Visual Guide](https://security-recipes.ai/how-to-use/)**: the qualified
search-discovery, CVE-to-plan, proof, rollback, review, and read-only MCP flow
in five diagrams.
- **[Docs](https://security-recipes.ai/docs/)**: site usage, agent consumption
patterns, and contribution guidance.
## Python remediation tooling
The Python suite is an optional execution companion to the documentation. It
can inspect a bounded workspace, select any of the 75 remediation playbooks,
create a durable run packet, record integrity-hashed evidence, and verify the
packet before agent or reviewer handoff. It remains local and conservative: it
does not merge code, deploy changes, or call external systems on its own.
```bash
python scripts/security_recipes_remediation_suite.py playbook list
python scripts/security_recipes_remediation_suite.py playbook inspect \
--playbook vulnerable-dependencies --workspace .
python scripts/security_recipes_remediation_suite.py playbook start \
--playbook vulnerable-dependencies --workspace . \
--finding finding.json --run-dir .security-recipes/runs/dependency-fix
python scripts/security_recipes_remediation_suite.py playbook verify \
--run-dir .security-recipes/runs/dependency-fix
```
The repository also includes domain-specific generators and evaluators for
playbooks that need richer evidence packs or runtime policy decisions. The
site and JSON registry remain useful without Python; the tools make the same
workflow contracts directly executable by CI, orchestrators, and approved
coding agents.
Deployment helpers worth knowing:
- `scripts/setup_digitalocean_droplet.sh`: Ubuntu droplet bootstrap with
Docker, host hardening, and optional Caddy-managed HTTPS.
- `scripts/configure_nginx_letsencrypt.sh`: host nginx reverse proxy setup for
teams that want Let's Encrypt on nginx instead of Caddy.
- `README.nginx-letsencrypt.md`: operator-focused walkthrough for the nginx
deployment path.
Recommended operating model:
1. Let existing SCA, SAST, secrets, CI, cloud, and ticketing systems produce
findings.
2. Attach a matching security-recipes.ai recipe and prompt.
3. Let the agent read only the files and MCP context needed for the finding.
4. Require tests and human review before merge.
5. Keep broad automation, write access, and deployment outside the first loop.
## Guidebook and execution tools
The site is a guidebook for remediation work: recipes, prompts, agent setup,
MCP/API integration notes, and review patterns. Runtime automation belongs in
the user's approved agent host, CI system, ticketing workflow, or scanner
platform rather than a site-hosted chatbot.
Python tools in `scripts/`, `tools/`, and `mcp_server.py` support maintainers
and self-hosters with playbook execution packets, evidence verification,
domain-specific evaluation and generation, validation, advisory import,
recipe search, and optional read-only MCP access.
## Optional MCP server
The MCP server is read-only by default. Its baseline role is to let
MCP-compatible agents search and retrieve recipes. Self-hosted deployments can
also configure it as a context hub for approved upstream MCP servers without
putting those credentials into the public site.
Retrieved context never grants mutation authority. Any connector that can
change repositories, tickets, secrets, deployments, or production systems must
be configured and approved separately by the calling host.
Common tools:
- `recipes_search`
- `recipes_list`
- `recipes_get`
- `recipes_cve_catalog_info`
- `recipes_cve_search`
- `recipes_cve_get`
- `recipes_match_finding`
- `recipes_playbooks_list`
- `recipes_playbook_get`
- `recipes_playbook_plan`
- `recipes_mcp_upstream_servers`
- `recipes_mcp_upstream_tools`
- `recipes_mcp_upstream_call`
- `recipes_mcp_upstream_context`
The MCP server accepts both generated recipe feeds:
- `/api/recipes.json` is the preferred agent feed with category, severity,
CVE/GHSA, ecosystem, and handoff metadata.
- `/recipes-index.json` remains supported for legacy consumers.
- `/recipes-browser.json` is the compact interactive-library feed. The
`/recipes/` page server-renders 18 crawlable recipe cards and an exactly
matching hydration seed, then requests the complete feed only when a visitor
focuses search, filters, sorts, follows a filtered URL, or loads more.
The complete CVE catalog is also available without MCP:
- `/api/cve-catalog/manifest.json` declares the exact date/severity policy,
source hashes, coverage counts, and shard inventory.
- `/api/cve-catalog/runtime-summary.json` is the small browser bootstrap with
coverage totals and content-derived cache versions for every runtime asset.
- `/api/cve-catalog/index.json` is a small manifest for the complete
publication-year partitions under `/api/cve-catalog/indexes/`. Offline
consumers can fetch only the years they need; neither a browser page load
nor an exact MCP lookup parses those partitions.
- `/api/cve-catalog/search` is the bounded, same-origin broad-search endpoint.
It is pinned to the shard-set revision declared by `runtime-summary.json`,
rate-limited at nginx, and returns at most 100 previews. The production MCP
image serves it from a read-only SQLite FTS database built and whole-file
verified against the same manifest. Focus alone and an incomplete
`CVE-YYYY-NNNN` identifier make no search request.
- `/api/cve-catalog/records/{cve}` is the bounded, same-origin exact-record
endpoint. Every request pins the shard-set revision, and the MCP service
verifies and opens only the one deterministic shard containing that CVE.
Current browsers use this endpoint instead of learning the shard namespace.
- `/api/cve-catalog/browser-index.json.gz` remains for one compatibility
window when an older runtime summary does not declare the search and record
APIs. Current browsers do not download it when the APIs are declared, so
visitors no longer pay the complete-corpus transfer or memory cost.
- Canonical CVE pages server-render their overview, affected-version evidence,
selected remediation authority, AI implementation and verification handoff,
sources, provenance, citation, and schema. They do not embed or hydrate the
catalog application. A compact link to the exact gzip JSON Lines shard remains
available for machine-readable provenance without adding a browser fetch.
- `/api/cve-catalog/search-indexable.json` is the compact, integrity-hashed
allowlist for canonical CVE pages, related-CVE links, and search discovery.
Its policy accepts only reviewed stable Markdown or complete AI enrichment
that passes the deterministic recipe-ready evidence contract. Every browser
result links to its local `/cve/