Security Recipes
REMOTE · SECURITY-RECIPES.AI
Read-only CVE intelligence, remediation playbooks, and agent setup guides. Not a scanner.
Available components
Last scanned (15 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 75 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 3793 tokens (~50/item across 75 items; 75 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "recipes_secure_context_eval_pack" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 75 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 75 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 0
- Server version: 4.1.6 → 4.1.8 functional
- 19 Nov 26 0
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 75 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 18 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- Server version: 4.1.3 → 4.1.6 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://security-recipes.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=security-recipes.ai | CN=YE2,O=Let's Encrypt,C=US | 7 Nov 2026 | 5 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6d1d160008fc0e0ff740dd45003c0a2f67b |
| SANs: security-recipes.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of security-recipes.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| security-recipes.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://security-recipes.ai/mcp | Verified | 200 | |
| http (plaintext) | http://security-recipes.ai/mcp | HTTPS enforced | 308 | https://security-recipes.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
recipes_mcp_servers_list Recipes Mcp Servers List ~40
Search the bundled catalog of publicly documented MCP servers and ecosystems.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | – | – | – |
| limit | integer | – | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_mcp_stdio_launch_boundary_pack Recipes Mcp Stdio Launch Boundary Pack ~44
Return MCP STDIO launch boundaries, profiles, decisions, and evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | – | – |
| launch_id | – | – | – |
| profile_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_mcp_tool_risk_contract Recipes Mcp Tool Risk Contract ~56
Return MCP tool annotation, trust, and session-combination risk evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| connector_id | – | – | – |
| decision | – | – | – |
| namespace | – | – | – |
| risk_tier | – | – | – |
| workflow_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_mcp_tool_surface_drift_pack Recipes Mcp Tool Surface Drift Pack ~56
Return pinned MCP tool descriptions, schemas, annotations, and drift evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | – | – |
| namespace | – | – | – |
| source_kind | – | – | – |
| surface_id | – | – | – |
| tool_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_mcp_upstream_call Recipes Mcp Upstream Call ~46
Call an allowed read-only tool on a configured upstream MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | – | – | – |
| server_id | string | yes | – |
| tool_name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_mcp_upstream_context Recipes Mcp Upstream Context ~46
Collect bounded context from configured upstream MCP servers for a remediation query.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | – |
| query | string | yes | – |
| server_ids | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_mcp_upstream_servers Recipes Mcp Upstream Servers ~24
List optional upstream MCP servers configured for this Security Recipes server.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
recipes_mcp_upstream_tools Recipes Mcp Upstream Tools ~35
List tools exposed by a configured upstream MCP server and show local allow decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_model_provider_routing_pack Recipes Model Provider Routing Pack ~61
Return model-provider route profiles, workflow mappings, and required evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | – | – |
| model_id | – | – | – |
| provider_id | – | – | – |
| risk_tier | – | – | – |
| route_id | – | – | – |
| workflow_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_playbook_get Recipes Playbook Get ~33
Get one complete remediation workflow, evidence, output, and Python contract.
| Name | Type | Req | Description |
|---|---|---|---|
| playbook_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_playbook_plan Recipes Playbook Plan ~41
Build a deterministic, read-only phase, gate, and evidence checklist for a finding.
| Name | Type | Req | Description |
|---|---|---|---|
| finding | – | – | – |
| playbook_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_playbooks_list Recipes Playbooks List ~41
List concise remediation playbook records, optionally filtered by query or category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_quality_report Recipes Quality Report ~38
Summarize recipe quality tiers and list recipes missing world-class signals.
| Name | Type | Req | Description |
|---|---|---|---|
| facet | – | – | – |
| limit | – | – | – |
| tier | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_refresh Recipes Refresh ~25
Refresh the in-memory copy of recipes-index.json.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_search Recipes Search ~55
Full-text search over security-recipes documents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | – | – | – |
| facets | – | – | – |
| limit | – | – | – |
| min_quality | – | – | – |
| query | string | yes | – |
| section | – | – | – |
| tags | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_attestation_pack Recipes Secure Context Attestation Pack ~57
Return secure-context attestation subjects, verification policy, and recertification state.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | – | – | – |
| source_id | – | – | – |
| status | – | – | – |
| subject_type | – | – | – |
| workflow_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_buyer_diligence_brief Recipes Secure Context Buyer Diligence Brief ~64
Return buyer and acquirer diligence evidence for the secure context layer.
| Name | Type | Req | Description |
|---|---|---|---|
| bet_id | – | – | – |
| buyer_id | – | – | – |
| objection_id | – | – | – |
| question_id | – | – | – |
| source_id | – | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_customer_proof_pack Recipes Secure Context Customer Proof Pack ~60
Return the customer proof contract for design partner and acquisition evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_id | – | – | – |
| event_id | – | – | – |
| gate_id | – | – | – |
| metric_id | – | – | – |
| risk_id | – | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_eval_pack Recipes Secure Context Eval Pack ~60
Return scenario-backed secure-context evals for retrieval, attestation, egress, and handoffs.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | – | – |
| minimum_score | – | – | – |
| scenario_id | – | – | – |
| scenario_type | – | – | – |
| workflow_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_evidence_contract Recipes Secure Context Evidence Contract ~52
Return the secure context evidence API and release contract.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | – | – | – |
| channel_id | – | – | – |
| endpoint_id | – | – | – |
| object_type_id | – | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_lineage_ledger Recipes Secure Context Lineage Ledger ~58
Return context lineage, reuse policy, stage requirements, hashes, and workflow envelopes.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | – | – |
| reuse_class | – | – | – |
| source_id | – | – | – |
| stage_id | – | – | – |
| workflow_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_trust_pack Recipes Secure Context Trust Pack ~51
Return context provenance, retrieval policy, source hashes, and workflow context packages.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | – | – | – |
| source_id | – | – | – |
| trust_tier | – | – | – |
| workflow_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_secure_context_value_model Recipes Secure Context Value Model ~61
Return the secure context value model for buyer, ROI, and acquisition diligence.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_id | – | – | – |
| question_id | – | – | – |
| scenario_id | – | – | – |
| segment_id | – | – | – |
| status | – | – | – |
| wedge_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recipes_server_info Recipes Server Info ~18
Return MCP server metadata and source-index configuration.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
recipes_workflow_control_plane Recipes Workflow Control Plane ~31
Return workflow control-plane policy for agents, reviewers, and MCP gateways.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Security Recipes MCP server?
Security Recipes is a hosted endpoint at https://security-recipes.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · security-recipes.ai
claude mcp add --transport http stevologic-security-recipes 'https://security-recipes.ai/mcp'
What is the Security Recipes MCP server?
Security Recipes is an MCP server listed in the public MCP registry as io.github.stevologic/security-recipes. Read-only CVE intelligence, remediation playbooks, and agent setup guides. Not a scanner. This page covers its hosted endpoint (https://security-recipes.ai/mcp).
Is the Security Recipes MCP server safe to use?
Security Recipes scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Security Recipes MCP server expose?
Security Recipes exposes 75 tools: recipes_server_info, recipes_mcp_upstream_servers, recipes_mcp_servers_list, recipes_mcp_server_get, recipes_mcp_upstream_tools, and 70 more. Their descriptions and schemas cost roughly 3,793 tokens of context every time the server is loaded.
Does the Security Recipes MCP server require authentication?
No. We connected to Security Recipes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Security Recipes MCP server still maintained?
Security Recipes is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Security Recipes MCP server?
VerifyMCP ran 12 checks on Security Recipes, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Security Recipes: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.