MCP servers observed by Lowdown
io.github.stevologic/security-recipes MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 75 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.stevologic/security-recipes
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.stevologic/security-recipes?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
75 tools on 2026-11-17:
recipes_a2a_agent_card_trust_profilerecipes_agent_capability_risk_registerrecipes_agent_handoff_boundary_packrecipes_agent_identity_ledgerrecipes_agent_memory_boundary_packrecipes_agent_skill_supply_chain_packrecipes_agent_trust_fabric_packrecipes_agentic_action_runtime_packrecipes_agentic_aivss_risk_scoring_packrecipes_agentic_app_intake_packrecipes_agentic_approval_receipt_packrecipes_agentic_assurance_packrecipes_agentic_catastrophic_risk_annexrecipes_agentic_control_plane_blueprintrecipes_agentic_entitlement_review_packrecipes_agentic_exposure_graphrecipes_agentic_incident_response_packrecipes_agentic_measurement_probe_packrecipes_agentic_posture_snapshotrecipes_agentic_protocol_conformance_packrecipes_agentic_readiness_scorecardrecipes_agentic_red_team_drill_packrecipes_agentic_red_team_replay_harnessrecipes_agentic_run_receipt_packrecipes_agentic_soc_detection_packrecipes_agentic_source_freshness_watchrecipes_agentic_standards_crosswalkrecipes_agentic_system_bomrecipes_agentic_telemetry_contractrecipes_agentic_threat_radarrecipes_browser_agent_boundary_packrecipes_context_egress_boundary_packrecipes_context_poisoning_guard_packrecipes_critical_infrastructure_secure_context_packrecipes_cve_catalog_inforecipes_cve_getrecipes_cve_searchrecipes_design_partner_pilot_packrecipes_enterprise_trust_center_exportrecipes_getrecipes_hosted_mcp_readiness_packrecipes_listrecipes_match_findingrecipes_mcp_authorization_conformance_packrecipes_mcp_connector_intake_packrecipes_mcp_connector_trust_packrecipes_mcp_elicitation_boundary_packrecipes_mcp_gateway_policyrecipes_mcp_risk_coverage_packrecipes_mcp_server_getrecipes_mcp_servers_listrecipes_mcp_stdio_launch_boundary_packrecipes_mcp_tool_risk_contractrecipes_mcp_tool_surface_drift_packrecipes_mcp_upstream_callrecipes_mcp_upstream_contextrecipes_mcp_upstream_serversrecipes_mcp_upstream_toolsrecipes_model_provider_routing_packrecipes_playbook_getrecipes_playbook_planrecipes_playbooks_listrecipes_quality_reportrecipes_refreshrecipes_searchrecipes_secure_context_attestation_packrecipes_secure_context_buyer_diligence_briefrecipes_secure_context_customer_proof_packrecipes_secure_context_eval_packrecipes_secure_context_evidence_contractrecipes_secure_context_lineage_ledgerrecipes_secure_context_trust_packrecipes_secure_context_value_modelrecipes_server_inforecipes_workflow_control_plane
MCP Registry declaration
- Registry name:
io.github.stevologic/security-recipes - Declared version: 1.0.0
- Status: active
- Declared hosts:
security-recipes.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.stevologic/security-recipes", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.stevologic/security-recipes?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).