recipes_server_info — Security Recipes MCP Tool
recipes_server_info
(recipes server info) is one of 75 tools on the
Security Recipes
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call recipes_server_info from your client
- Claude Code Security Recipes recipes_server_info run in your project directory
- Claude Desktop Security Recipes recipes_server_info ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Security Recipes recipes_server_info ~/.cursor/mcp.json
- VS Code Security Recipes recipes_server_info .vscode/mcp.json
- Zed Security Recipes recipes_server_info ~/.config/zed/settings.json
- Windsurf Security Recipes recipes_server_info ~/.codeium/windsurf/mcp_config.json
- Cline Security Recipes recipes_server_info ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Security Recipes recipes_server_info ~/.gemini/settings.json
- Grok Security Recipes recipes_server_info .mcp.json (in your project root)
- ChatGPT Security Recipes recipes_server_info Settings → Connectors → Advanced → Developer mode
- Claude.ai Security Recipes recipes_server_info Settings → Connectors → Add custom connector
- LangChain Security Recipes recipes_server_info pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http security-recipes https://security-recipes.ai/mcpOther tools on this server
- 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
- recipes_agentic_incident_response_pack
- recipes_agentic_action_runtime_pack
- recipes_agent_trust_fabric_pack
- recipes_browser_agent_boundary_pack
- recipes_agentic_measurement_probe_pack
- recipes_agentic_telemetry_contract
- recipes_agentic_soc_detection_pack
- recipes_enterprise_trust_center_export
- recipes_secure_context_value_model
- recipes_design_partner_pilot_pack
- recipes_secure_context_buyer_diligence_brief
- recipes_secure_context_customer_proof_pack
- recipes_secure_context_evidence_contract
- recipes_hosted_mcp_readiness_pack
- recipes_match_finding
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.