IT-Grundschutz Kompendium

{
  "id": "aix_1de36c035e",
  "name": "IT-Grundschutz Kompendium",
  "operator": "(unclaimed - source: pulsemcp · publisher: github.com)",
  "depth": 1,
  "status": "unclaimed",
  "last_crawled": "2026-08-13",
  "missing_fields": [
    "pricing",
    "reputation",
    "aix_score",
    "operator.identity"
  ],
  "skills": [
    "general-tools"
  ],
  "protocols": {
    "mcp": "https://grundschutz-mcp.kurtz.to/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": null,
  "aix_score": null,
  "verification": {
    "identity": "none",
    "health": "liveness-only",
    "pricing": "unknown",
    "last_check": "2026-08-13T08:01:08.014Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://www.pulsemcp.com/servers/ay-kay-it-grundschutz"
    },
    {
      "label": "repository",
      "url": "https://github.com/ay-kay/grundschutz-mcp"
    }
  ],
  "avatar": "https://github.com/ay-kay.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/ay-kay"
    }
  ],
  "public_stats": {
    "gh_stars": 2
  },
  "unreachable": false,
  "profile": {
    "mcp_server": "grundschutz-mcp",
    "mcp_version": "0.2.1",
    "tool_count": 14,
    "tools": [
      {
        "name": "list_layers",
        "description": "Return all 10 BSI Grundschutz layers (APP, CON, DER, IND, INF, ISMS, NET, OPS, ORP, SYS)."
      },
      {
        "name": "list_modules",
        "description": "List Bausteine, optionally filtered. Returns the WHOLE catalogue by default.\n\nTo get every Baustein of one implementation-priority class, pass\n``priority`` = ``R1`` (highest; the 15 Bausteine BSI says to do first,\ne.g. ISMS.1, the four ORP.* and six OPS.1.1.* modules, CON.3, CON.6,\nDER.1, DER.2.1), ``R2`` or ``R3``. Do NOT list all modules and count\nby eye - use the ``priority`` filter.\n\nThe response is an envelope ``{\"modules\": [...], \"total_count\": N,\n\"returned_count\": M, \"truncated\": bool}``. ``truncated`` is true only\nwhen ``limit`` cut the result short; the default limit (200) covers the\nfull 111-module catalogue, so a default call is always complete.\n"
      },
      {
        "name": "get_module",
        "description": "Return one Baustein with description, threat situation, baustein-specific threat scenarios, and its requirements."
      },
      {
        "name": "list_module_threats",
        "description": "Return the baustein-specific named threat scenarios of one Baustein.\n\nThese are the sub-sections of the Baustein's Gefährdungslage in the BSI\nXML (e.g. for CON.3: \"Ransomware\", \"Fehlende Wiederherstellungstests\",\n\"Ungeeignete Aufbewahrung der Speichermedien\" etc.). Not to be\nconfused with the 47 elementary threats (G 0.x), which you can fetch\nvia get_threats_for_requirement.\n"
      },
      {
        "name": "list_requirements",
        "description": "Return the requirements of one Baustein. Filter by level (Basis|Standard|Hoch)."
      },
      {
        "name": "get_requirement",
        "description": "Return one requirement with full prose, module context, assigned roles, and protection goals.\n\n``protection_goals`` lists the C/I/A Grundwerte the BSI\nKreuzreferenztabelle assigns to this requirement. BSI fills this\nonly for a subset of requirements, so an empty list means BSI\nassigned none - not that data is missing.\n"
      },
      {
        "name": "get_cross_references",
        "description": "Return the codes that a requirement's prose references."
      },
      {
        "name": "list_threats",
        "description": "Return all 47 elementary BSI threats (G 0.1 .. G 0.47)."
      },
      {
        "name": "get_threat",
        "description": "Return one elementary threat with its full description."
      },
      {
        "name": "get_threats_for_requirement",
        "description": "Return the threats a requirement addresses, plus the requirement's protection goals.\n\n``protection_goals`` (C/I/A) belongs to the requirement as a whole\n(BSI Kreuzreferenztabelle Grundwerte), not to individual threats, so\nit is reported once at the top level. Empty means BSI assigned none.\n"
      },
      {
        "name": "get_requirements_for_threat",
        "description": "Return all requirements that address a given elementary threat."
      },
      {
        "name": "search",
        "description": "**Recommended default search.** Hybrid keyword + semantic over the\nBSI catalog via Reciprocal Rank Fusion.\n\nUse this for almost every search question - it handles both phrased\nnatural-language queries (\"Wie sichere ich Backups gegen Erpressung?\")\nand concrete named entities (\"Ransomware\", \"MFA\", \"SAP ABAP\") well,\nbecause it fuses FTS5 keyword matching with the dense embedding\nsearch.\n\n``entity_types`` filters to subsets of {\"requirement\", \"module\",\n\"threat\"}; default is all three. Hits carry ``rrf_score`` (higher\nis better) plus the per-retriever ranks ``keyword_rank`` and\n``semantic_rank`` so the caller can see which path found them.\n"
      },
      {
        "name": "search_keyword",
        "description": "FTS5 keyword search. Strict matching - use for BSI codes,\nproduct names, malware family names or any other exact term where\nyou do NOT want semantic generalisation.\n\nFor most questions, prefer the ``search`` tool which combines this\nwith semantic retrieval. FTS5 syntax (``AND``/``OR``/``NEAR``,\ndouble-quoted phrases) is supported in ``query``.\n"
      },
      {
        "name": "search_semantic",
        "description": "Pure dense vector search. Use only when you want semantic\ngeneralisation without keyword bias - e.g. exploring conceptually\nadjacent topics.\n\nFor most questions, prefer the ``search`` tool. Dense retrieval\nalone tends to exhibit term-bias on rare proper nouns (it may\ncluster \"Verschlüsselungstrojaner\" with all encryption topics\nrather than ransomware specifically).\n"
      }
    ],
    "profiled_at": "2026-08-13T08:01:08.014Z"
  }
}