Home / MCP registry index / io.github.stevologic/security-recipes
Security Recipes
io.github.stevologic/security-recipes in the official MCP registry.
Endpoint https://security-recipes.ai/mcp. Source: github.com/stevologic/security-recipes.ai.
The registry describes it as: Read-only CVE intelligence, remediation playbooks, and agent setup guides. Not a scanner.
We read its 75 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
recipes_server_info recipes_mcp_upstream_servers recipes_mcp_servers_list recipes_mcp_server_get recipes_mcp_upstream_tools recipes_mcp_upstream_call recipes_mcp_upstream_context recipes_refresh recipes_search recipes_list recipes_get recipes_playbooks_list recipes_playbook_get recipes_playbook_plan recipes_cve_catalog_info recipes_cve_search recipes_cve_get recipes_quality_report recipes_workflow_control_plane recipes_mcp_gateway_policy recipes_agentic_assurance_pack recipes_agent_identity_ledger recipes_agentic_entitlement_review_pack recipes_agentic_approval_receipt_pack recipes_mcp_connector_trust_pack recipes_mcp_connector_intake_pack recipes_mcp_stdio_launch_boundary_pack recipes_mcp_authorization_conformance_pack recipes_mcp_elicitation_boundary_pack recipes_mcp_tool_risk_contract recipes_mcp_tool_surface_drift_pack recipes_agentic_red_team_drill_pack recipes_agentic_red_team_replay_harness recipes_agentic_readiness_scorecard recipes_agent_capability_risk_register recipes_agent_memory_boundary_pack recipes_agent_skill_supply_chain_pack recipes_agent_handoff_boundary_pack recipes_a2a_agent_card_trust_profile recipes_agentic_system_bom recipes_agentic_run_receipt_pack recipes_secure_context_trust_pack recipes_secure_context_attestation_pack recipes_secure_context_lineage_ledger recipes_secure_context_eval_pack recipes_context_poisoning_guard_pack recipes_context_egress_boundary_pack recipes_agentic_threat_radar recipes_agentic_standards_crosswalk recipes_agentic_source_freshness_watch recipes_mcp_risk_coverage_pack recipes_agentic_protocol_conformance_pack recipes_agentic_control_plane_blueprint recipes_agentic_exposure_graph recipes_agentic_posture_snapshot recipes_agentic_aivss_risk_scoring_pack recipes_agentic_app_intake_pack recipes_model_provider_routing_pack recipes_agentic_catastrophic_risk_annex recipes_critical_infrastructure_secure_context_pack and 15 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-stevologic-security-recipes)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.