原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Security Recipes

作者:stevologic版本 1.0.0i★ 2i在云端运行
注册名称io.github.stevologic/security-recipes

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 网络安全

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3Connect4
https://security-recipes.ai/mcp

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3Connect4
https://security-recipes.ai/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月10日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • recipes_server_info

    Return MCP server metadata and source-index configuration.

  • recipes_mcp_upstream_servers

    List optional upstream MCP servers configured for this Security Recipes server.

  • recipes_mcp_servers_list

    Search the bundled catalog of publicly documented MCP servers and ecosystems.

  • recipes_mcp_server_get

    Return one publicly documented MCP server with official setup and safety guidance.

  • recipes_mcp_upstream_tools

    List tools exposed by a configured upstream MCP server and show local allow decisions.

  • recipes_mcp_upstream_call

    Call an allowed read-only tool on a configured upstream MCP server.

  • recipes_mcp_upstream_context

    Collect bounded context from configured upstream MCP servers for a remediation query.

  • recipes_refresh

    Refresh the in-memory copy of recipes-index.json.

  • recipes_search

    Full-text search over security-recipes documents.

  • recipes_list

    List recipes with optional metadata filtering.

  • recipes_get

    Get a full recipe record by slug or path.

  • recipes_playbooks_list

    List concise remediation playbook records, optionally filtered by query or category.

  • recipes_playbook_get

    Get one complete remediation workflow, evidence, output, and Python contract.

  • recipes_playbook_plan

    Build a deterministic, read-only phase, gate, and evidence checklist for a finding.

  • recipes_cve_catalog_info

    Return the complete Medium/High/Critical CVE catalog scope, coverage, provenance, and counts.

  • recipes_cve_search

    Search every in-scope Medium/High/Critical CVE; use recipes_cve_get for complete details.

  • recipes_cve_get

    Get evidence, recipe authority, and a bounded code/config/file change plan for one exact CVE.

  • recipes_quality_report

    Summarize recipe quality tiers and list recipes missing world-class signals.

  • recipes_workflow_control_plane

    Return workflow control-plane policy for agents, reviewers, and MCP gateways.

  • recipes_mcp_gateway_policy

    Return generated MCP gateway policy for scoped tool access and runtime controls.

  • recipes_agentic_assurance_pack

    Return enterprise assurance controls, workflow evidence, and AI/Agent BOM seed.

  • recipes_agent_identity_ledger

    Return agent non-human identity, delegation, scope, and audit contracts.

  • recipes_agentic_entitlement_review_pack

    Return expiring agent entitlement leases, access reviews, and scope evidence.

  • recipes_agentic_approval_receipt_pack

    Return scope-bound approval receipt profiles, workflow requirements, and evidence.

  • recipes_mcp_connector_trust_pack

    Return MCP connector trust tiers, controls, evidence, and workflow namespace coverage.

  • recipes_mcp_connector_intake_pack

    Return MCP connector intake decisions, risk findings, gaps, and promotion plans.

  • recipes_mcp_stdio_launch_boundary_pack

    Return MCP STDIO launch boundaries, profiles, decisions, and evidence.

  • recipes_mcp_authorization_conformance_pack

    Return MCP authorization conformance, scope-drift, and token-boundary evidence.

  • recipes_mcp_elicitation_boundary_pack

    Return MCP form-mode and URL-mode elicitation boundary evidence.

  • recipes_mcp_tool_risk_contract

    Return MCP tool annotation, trust, and session-combination risk evidence.

  • recipes_mcp_tool_surface_drift_pack

    Return pinned MCP tool descriptions, schemas, annotations, and drift evidence.

  • recipes_agentic_red_team_drill_pack

    Return adversarial drills for agentic remediation workflows and MCP controls.

  • recipes_agentic_red_team_replay_harness

    Return replay fixtures, expected decisions, and evidence gates for red-team drills.

  • recipes_agentic_readiness_scorecard

    Return generated scale, pilot, gate, or block decisions for agentic workflows.

  • recipes_agent_capability_risk_register

    Return capability-based residual risk scores for agentic workflows.

  • recipes_agent_memory_boundary_pack

    Return agent memory classes, workflow profiles, TTLs, and persistence decisions.

  • recipes_agent_skill_supply_chain_pack

    Return agent skill provenance, permission, isolation, and supply-chain decisions.

  • recipes_agent_handoff_boundary_pack

    Return agent handoff boundary profiles, protocol controls, and workflow maps.

  • recipes_a2a_agent_card_trust_profile

    Return A2A Agent Card intake profiles, trust controls, and sample decisions.

  • recipes_agentic_system_bom

    Return the Agentic System BOM for workflows, agents, identities, MCP tools, and evidence.

  • recipes_agentic_run_receipt_pack

    Return agent run receipt templates for identity, context, tools, egress, approval, and evidence.

  • recipes_secure_context_trust_pack

    Return context provenance, retrieval policy, source hashes, and workflow context packages.

  • recipes_secure_context_attestation_pack

    Return secure-context attestation subjects, verification policy, and recertification state.

  • recipes_secure_context_lineage_ledger

    Return context lineage, reuse policy, stage requirements, hashes, and workflow envelopes.

  • recipes_secure_context_eval_pack

    Return scenario-backed secure-context evals for retrieval, attestation, egress, and handoffs.

  • recipes_context_poisoning_guard_pack

    Return context-poisoning scan results for registered secure-context sources.

  • recipes_context_egress_boundary_pack

    Return context egress data classes, destination classes, and workflow boundary policy.

  • recipes_agentic_threat_radar

    Return current source-backed agentic AI threat signals and product priorities.

  • recipes_agentic_standards_crosswalk

    Return standards-to-evidence mappings for agentic AI, MCP, and prompt-injection guidance.

  • recipes_agentic_source_freshness_watch

    Return source-freshness and standards-drift evidence for SecurityRecipes.

  • recipes_mcp_risk_coverage_pack

    Return OWASP MCP and agentic-skill risk coverage mapped to generated evidence.

  • recipes_agentic_protocol_conformance_pack

    Return MCP/A2A protocol conformance evidence and buyer-ready drift controls.

  • recipes_agentic_control_plane_blueprint

    Return the acquisition-ready agentic control plane architecture and buyer evidence map.

  • recipes_agentic_exposure_graph

    Return risk-ranked agentic exposure paths across context, identities, MCP tools, and evidence.

  • recipes_agentic_posture_snapshot

    Return the generated enterprise posture snapshot for agentic AI and MCP operations.

  • recipes_agentic_aivss_risk_scoring_pack

    Return AIVSS-aligned agentic risk scores, SLAs, evidence, and hosted MCP wedges.

  • recipes_agentic_app_intake_pack

    Return generated agentic app launch-review profiles and decisions.

  • recipes_model_provider_routing_pack

    Return model-provider route profiles, workflow mappings, and required evidence.

  • recipes_agentic_catastrophic_risk_annex

    Return the severe-risk annex for high-impact agentic AI runtime decisions.

  • recipes_critical_infrastructure_secure_context_pack

    Return the generated critical-infrastructure secure-context profile.

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 stevologic 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 783 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 60 个工具描述,未发现针对 AI 的隐藏指令

与“网络安全”中的其他服务器比较i

  • 星标数多于此分类中其他 1017 个服务器的 78%
  • 发布到注册中心的时间比此分类中其他 1017 个服务器的 38% 更新
  • 基础检查结果等于或优于此分类中其他 1017 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Security Recipes 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(1.0.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Robin: AI-Powered Dark Web OSINT, HOL Guard, UniFi Network MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Robin: AI-Powered Dark Web OSINT

Dark web OSINT over Tor: search onion engines, scrape pages, report with your own model.

作者:apurvsinghgautam正在增长★ 794339天前更新

在你的电脑上运行

HOL Guard

Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.

作者:hashgraph-online广泛使用↓ 7083/周★ 10816天前更新

在你的电脑上运行

UniFi Network MCP

Manage UniFi Network devices, clients, firewall, VLANs, VPNs, and more via MCP.

作者:sirkirby广泛使用↓ 1.1万/周★ 10298个月前更新

在你的电脑上运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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 recordCVE evidence to bounded agent plan
Proof and human reviewRead-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

PathPurpose
content/Recipes, documentation, remediation guides, and agent setup pages.
eleventy.config.jsSite 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.pyOptional read-only MCP server for recipe search and approved upstream MCP context.
mcp-server.toml.exampleMCP server configuration template.
DockerfileSite image.
Dockerfile.mcp-serverOptional MCP server image.
docker-compose.ymlProduction-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

只显示了开头部分;其余内容请在仓库中阅读