Is the Stevologic Security Recipes MCP server down?

mcp-registry/io.github.stevologic/security-recipes · v4.1.0

healthy
Last checked 2026-10-22 03:30 UTC · handshake 79ms

As of 2026-10-22 03:30 UTC, the Stevologic Security Recipes MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
100%
checks observed
4,216
outages (90d)
5
tools
75

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

Install Stevologic Security Recipes MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 4 warning(s) across 75 tool(s); ~10,646 tokens of tool definitions.
Scores higher than 5% of 15,538 MCP servers Glimind has audited.
Its tool list costs an agent ~10,646 tokens per session — more than 80% of servers.
68 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints16
Token cost75
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (4)

75 of 75 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: recipes_a2a_agent_card_trust_profile, recipes_agent_capability_risk_register, recipes_agent_handoff_boundary_pack, recipes_agent_identity_ledger, recipes_agent_memory_boundary_pack and 70 more

75 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

305 parameter(s) across 72 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: recipes_a2a_agent_card_trust_profile, recipes_agent_capability_risk_register, recipes_agent_handoff_boundary_pack, recipes_agent_identity_ledger, recipes_agent_memory_boundary_pack and 67 more

4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: recipes_agentic_action_runtime_pack, recipes_agentic_posture_snapshot, recipes_agentic_run_receipt_pack, recipes_secure_context_buyer_diligence_brief

Auto-fix: 20 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 72 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.stevologic%2Fsecurity-recipes/fixes

recipes_agentic_action_runtime_pack 1 change 
{
  "name": "recipes_agentic_action_runtime_pack",
  "description": "Return action classes, workflow action envelopes, runtime policy, and evidence.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "decision": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "risk_tier": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "workflow_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "action_class_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Recipes Agentic Action Runtime Pack"
}
recipes_agentic_posture_snapshot 1 change 
{
  "name": "recipes_agentic_posture_snapshot",
  "description": "Return the generated enterprise posture snapshot for agentic AI and MCP operations.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "finding_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "workflow_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "minimum_score": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "risk_factor_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "posture_decision": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Recipes Agentic Posture Snapshot"
}
recipes_agentic_readiness_scorecard 1 change 
{
  "name": "recipes_agentic_readiness_scorecard",
  "description": "Return generated scale, pilot, gate, or block decisions for agentic workflows.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "decision": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "workflow_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "minimum_score": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Recipes Agentic Readiness Scorecard"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.stevologic/security-recipes"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.stevologic/security-recipes"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.stevologic%2Fsecurity-recipes.svg)](https://glimind.com/server/mcp-registry%2Fio.github.stevologic%2Fsecurity-recipes?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.stevologic%2Fsecurity-recipes?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.stevologic%2Fsecurity-recipes.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.stevologic%2Fsecurity-recipes.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.stevologic%2Fsecurity-recipes?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0fcbfa91a3c6e7c2…, first seen 2026-10-17, included at leaf 16517 of 43,298. Version history · verify what your client received.

Tools (75)

Compare: most reliable knowledge servers · most reliable search servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Stevologic Security Recipes MCP server down right now?

As of 2026-10-22 03:30 UTC, the Stevologic Security Recipes MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Stevologic Security Recipes MCP server provide?

Stevologic Security Recipes MCP server advertises 75 tools, including recipes_a2a_agent_card_trust_profile, recipes_agent_capability_risk_register, recipes_agent_handoff_boundary_pack, recipes_agent_identity_ledger, recipes_agent_memory_boundary_pack.

How do I install Stevologic Security Recipes MCP server?

Point your MCP client at this streamable-http endpoint: https://security-recipes.ai/mcp

Is the Stevologic Security Recipes MCP server safe to connect to an AI agent?

Glimind scanned all 75 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Stevologic Security Recipes MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve