Security Recipes

Name: Security Recipes
Author: stevologic

by stevologicversion 1.0.0i★ –iRuns in the cloud

Registry nameio.github.stevologic/security-recipes

Install

Overview

Description from the maker (original English)

Read-only CVE intelligence, remediation playbooks, and agent setup guides. Not a scanner.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://security-recipes.ai/mcp

Run this in your terminal

claude mcp add --transport http security-recipes https://security-recipes.ai/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "security-recipes": {
      "url": "https://security-recipes.ai/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "security-recipes": {
      "type": "http",
      "url": "https://security-recipes.ai/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://security-recipes.ai/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account stevologic, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32558 servers in this category
Published to the registry more recently than 30% of the other 32558 servers in this category
Basic checks equal to or better than 100% of the other 32558 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Security Recipes safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FactLot

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FactLot

by 9mp96ygnbk-alt

Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 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 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 for an exact vulnerability or the AI Vulnerability Remediation Playbooks for the evidence-to-patch workflow. Agent-specific guides cover Codex, Claude Code, Cursor, GitHub Copilot, Devin, Shiba Studio, Hermes Desktop, and OpenClaw. The Visual Guide 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.

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 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. It ties the dependency-only change to the reviewed pull request, 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 rev

Only the beginning is shown; read the rest in the repo

Security Recipes

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FactLot

README from the maker

security-recipes.ai

Current product and workflow

Qualified search discovery

What this project is for

What ships

Repository map

Core content areas