ISM MCP Server
You can query the Australian Cyber Security Centre Information Security Manual (ISM) across versions, controls, and baselines through MCP tools, resources, and prompts.
List all published ISM versions, including historical, current, and future releases.
Fetch version metadata such as title, version, last-modified, and OSCAL version.
Browse the hierarchical ISM structure: chapters, guidelines, sections, and control counts.
List and filter controls by applicability, group/section, and label prefix.
Full-text search controls across labels, titles, statements, and group paths.
Retrieve one or many controls by OSCAL id or human label, as JSON or Markdown.
Compare two ISM releases and see added, removed, and modified controls.
List OSCAL profiles for NC/OS/P/S/TS classification baselines and Essential Eight ML1/ML2/ML3.
Resolve and retrieve the controls included in a chosen profile or maturity level.
Inspect cache and offline data status.
Use resources for full catalogs, single-control Markdown, and resolved profile catalogs.
Use prompts for compliance checks and change-management briefs.
Run locally over stdio or as a remote MCP Streamable HTTP endpoint.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ISM MCP Server what's the latest ISM version?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ism-mcp
A Model Context Protocol server that serves the Australian Cyber Security Centre (ACSC) Information Security Manual (ISM) to MCP-capable LLM clients (Claude Desktop, VS Code, Cursor, Continue, etc.).
Data is sourced live from the official ASD/ACSC OSCAL mirror:
Each git tag in that repository is one published ISM release. The server discovers tags dynamically via the GitHub API, so:
All historical versions back to
v2022.09.14are available.The current version is whichever tag is newest.
Future versions automatically appear the moment ASD publishes a new tag — no code changes or redeploys required.
Catalog and profile JSON is cached on disk (default
~/.cache/ism-mcp/, override with ISM_MCP_CACHE_DIR). Tag listings are
refreshed every six hours (override with ISM_MCP_TAGS_TTL_MS).
Capabilities
Tools
Tool | Purpose |
| Enumerate every published ISM release (tag, id, SHA, date). |
| OSCAL metadata + control/group counts for a version. |
| Hierarchical chapter/guideline structure with control counts. |
| Paginated list of controls, filterable by applicability / group / label prefix. |
| Full-text search across labels, titles, statements, and group paths. |
| Full detail for a single control by OSCAL id or human label (e.g. |
| Full detail for multiple controls in one call, with unmatched identifiers and optional deduplication. |
| Diff two ISM releases — added, removed, and modified controls. |
| List the eight OSCAL profiles (NC / OS / P / S / TS + E8 ML1/2/3). |
| Resolved set of controls for a given baseline or Essential Eight maturity level. |
| Inspect the local cache. |
Resources (templates)
ism://catalog/{version}— full OSCAL catalog JSON (uselatestor e.g.2026.03.24).ism://catalog/{version}/control/{controlId}— a single control rendered as Markdown.ism://profile/{version}/{profile}— OSCAL resolved-profile catalog for a baseline.
Prompts
ism_compliance_check— generate a structured compliance assessment of a system against a baseline.ism_change_brief— produce a change-management brief between two ISM releases.
Related MCP server: fedramp-docs-mcp
Install / build
npm install
npm run buildThe compiled entrypoint is dist/index.js and is exposed as the ism-mcp bin.
Run
The server speaks MCP over stdio:
node dist/index.jsFor interactive exploration, use the official inspector:
npm run inspectWire it into a client
VS Code (.vscode/mcp.json or settings)
{
"servers": {
"ism": {
"command": "node",
"args": ["/absolute/path/to/ism-mcp/dist/index.js"],
},
},
}Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ism": {
"command": "node",
"args": ["/absolute/path/to/ism-mcp/dist/index.js"],
},
},
}Optional environment
Variable | Purpose |
| Override on-disk cache directory. |
| Tag-list cache TTL in milliseconds (default 6h). |
Example prompts to try
"What ISM versions are available?"
"Show me GOV-01 from the latest ISM, in Markdown."
"Search for ISM controls about multi-factor authentication that apply to PROTECTED."
"Compare ISM 2025.12.9 with the latest release and summarise the changes."
"List the controls in the Essential Eight ML2 baseline for the latest ISM."
Data and licensing
The ISM is published by the Australian Signals Directorate. See the upstream repository and https://www.cyber.gov.au for terms of use. This server is an unaffiliated tool that consumes the publicly published OSCAL data.
CI / CD
Three GitHub Actions workflows ship with the repo:
.github/workflows/ci.yml— type-checks, builds, and runs the offline smoke test on every push and PR. On normalmainpushes it still creates a version tag and dispatches the release workflow; when.github/upstream-ism-tag.txtchanges, it skips that dispatch so the marker-triggered release path owns the deployment..github/workflows/release.yml— runs when.github/upstream-ism-tag.txtchanges onmain(or by manual dispatch), bundles the latest data, builds, packs the tarball, generates checksums, creates the version tag and GitHub Release with the tarball anddata/index.jsonattached, updates a rollinglatestgit tag to the released commit, and (optionally) publishes to npm. If Cloudflare credentials are configured, it deploys a Cloudflare Worker that serves the site and exposes the MCP Streamable HTTP endpoint at/mcp(manual dispatch can disable this viadeploy_cloudflare=false)..github/workflows/upstream-sync.yml— checks the upstream ACSC ISM OSCAL repository on a daily schedule (or manual dispatch). When a new ISM tag is published upstream, it updates.github/upstream-ism-tag.txt, bumps the package patch version, commits the update tomain, and lets the marker-triggered release workflow create the GitHub Release and deploy to Cloudflare Workers.
One-time repository setup
Settings → Actions → General → Workflow permissions: Read and write.
(Optional) configure repository credentials for npm publish on release.
Update the
repository,homepage, andbugsfields inpackage.json(replaceOWNER).(Optional) configure Cloudflare account credentials in repository secrets to enable Workers deployment on release.
Cutting a release
# bump version
npm version patch # or minor / major
git push --follow-tagsManual releases run CI first; when CI succeeds on main, it creates the version tag and dispatches release.yml, which builds an offline-ready ism-mcp-<version>.tgz, attaches it to the GitHub Release, and (optionally) publishes the package to npm and deploys the Cloudflare Worker endpoint.
Upstream ISM releases are also checked automatically once per day. If a new upstream tag is detected, the sync workflow updates .github/upstream-ism-tag.txt, bumps the package version, pushes the update to main, and the release workflow creates the GitHub Release and deploys the Cloudflare Worker endpoint.
For remote AI clients, add the remote MCP server with this URL:
https://ism.mcp.zta.au/mcp
{
"servers": {
"ism": {
"type": "http",
"url": "https://ism.mcp.zta.au/mcp",
},
},
}Remote MCP / HTTP transport
Beyond stdio, ism-mcp also speaks MCP Streamable HTTP so it can be hosted as a remote endpoint that AI tools query over the network.
# run as an HTTP server on :8080
MCP_TRANSPORT=http PORT=8080 node dist/index.js
# or via flag
node dist/index.js --httpEndpoints:
POST /mcp— JSON-RPC over Streamable HTTP (per-session viaMcp-Session-Idheader).GET /health— liveness probe.GET /— plain-text usage hint.GET /.well-known/oauth-protected-resource/mcp— protected resource metadata for MCP OAuth discovery.GET /.well-known/oauth-authorization-server— authorization server metadata.POST /register— dynamic client registration.POST /token— token issuance for registered clients usingclient_credentials.
The hosted Cloudflare deployment supports dynamic client registration and client_credentials token exchange in addition to unauthenticated MCP access.
For durable client registrations and issued tokens across Worker restarts, bind a Cloudflare KV namespace as AUTH_KV. If AUTH_KV is not configured, the Worker falls back to in-memory auth state.
Environment variables:
Variable | Purpose |
|
|
| Bind address (defaults: |
| URL path for the MCP endpoint (default |
Connect a client to the remote endpoint
Hosted endpoint: https://ism.mcp.zta.au/mcp
// VS Code .vscode/mcp.json
{
"servers": {
"ism": {
"type": "http",
"url": "https://ism.mcp.zta.au/mcp",
},
},
}Available Tools
11 toolscache_infoInspect ISM MCP storageA
Reports the bundled offline data directory, the writable user cache directory, sizes, file counts, and whether the server is running in offline mode (ISM_MCP_OFFLINE).
Inputs: no named parameters.
compare_versionsCompare two ISM versionsA
Computes the diff between two ISM releases: controls added, removed, and modified (title, statement, or applicability changes). Useful for change-management and gap analysis.
Inputs: to (required), from (required), includeBodies.
get_controlGet a single ISM controlA
Returns the full detail (title, group path, applicability, statement) for a single ISM control. Accepts either the OSCAL id (e.g. ism-principle-gov-01) or the human label (e.g. GOV-01).
Inputs: controlId (required), format, version.
get_controlsGet multiple ISM controlsB
Returns full detail for multiple ISM controls in one call. Accepts OSCAL ids and/or human labels (e.g. GOV-01).
Inputs: controlIds (required), format, version, deduplicate.
get_profile_controlsGet controls for an ISM OSCAL profileB
Returns the resolved set of controls included in a given ISM OSCAL profile (classification baseline or Essential Eight maturity level) for a given version.
Inputs: profile (required), limit, offset, version.
get_version_metadataGet ISM version metadataA
Returns OSCAL metadata (title, version, last-modified, oscal-version) for a given ISM release. Use "latest" or omit to get the most recent.
Inputs: version.
list_controlsList ISM controlsC
Returns a paginated, filtered list of ISM controls. Supports filters by applicability, group/section name (substring), and label prefix (e.g. "GOV", "AC", "PHYS").
Inputs: group, limit, offset, version, +2 more.
list_groupsList ISM groups (chapters and guidelines)B
Returns the hierarchical group structure of the ISM catalog (chapters, guidelines, sections) with control counts at each level.
Inputs: version, maxDepth.
list_profilesList ISM OSCAL profilesA
Lists the OSCAL profiles published alongside each ISM release: the five classification baselines (NC, OS, P, S, TS) and the three Essential Eight maturity levels (ML1, ML2, ML3).
Inputs: no named parameters.
list_versionsList ISM versionsB
Lists every published ISM release (historical, current, and any future tags as soon as they appear upstream). Returns tag, version id, commit SHA, and release date parsed from the tag.
Inputs: limit, refresh.
search_controlsSearch ISM controlsA
Full-text search across ISM control labels, titles, statements, and group paths. Combine with applicability/group/labelPrefix filters.
Inputs: query (required), group, limit, offset, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: cache_info handles offline cache, compare_versions diffs releases, get_control/get_controls retrieve details, get_profile_controls gets controls for profiles, get_version_metadata gets release metadata, list_controls filters controls, list_groups shows hierarchy, list_profiles lists baselines, list_versions lists releases, and search_controls performs full-text search. No two tools have overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case: cache_info, compare_versions, get_control, get_controls, get_profile_controls, get_version_metadata, list_controls, list_groups, list_profiles, list_versions, search_controls. The verbs are descriptive and the nouns clearly indicate the resource.
11 tools is well-scoped for an ISM reference server. It provides sufficient granularity for querying, searching, listing, and comparing controls, profiles, and versions without being excessive or minimal.
The tool set covers all essential operations for exploring the ISM catalog: retrieving individual or multiple controls, listing with filters, full-text search, accessing version metadata, listing versions and profiles, getting profile controls, comparing releases, and checking cache status. No obvious gaps for a read-only reference server.
Maintenance
Related MCP Connectors
data.gov.au MCP — Australia open-data CKAN catalogue.
MCP server for accessing curated awesome list documentation
Read-only MCP server over the developer docs for the portfolio's JSON API, MCP, A2A and NLWeb.
Hosted MCP server for finding authoritative primary data sources and official portals.
Related MCP Servers
- AlicenseAqualityCmaintenanceAgent-friendly query layer over the ASD Information Security Manual, served via MCP. Enables agents to discover and interrogate ISM controls using plain language queries and coverage tracking for IRAP review.17MIT
- FlicenseAqualityDmaintenanceAn unofficial MCP server that exposes public FedRAMP 20x documentation as deterministic, citable lookup tools for AI assistants, with every response citing the exact upstream source.7-
- AlicenseCqualityDmaintenanceMCP server for retrieving clinical standard content from the CDISC Library, supporting controlled terminology, ADaM, SDTM, CDASH, SEND metadata, and search.317MIT
- AlicenseAqualityFmaintenanceEnables querying Swiss cybersecurity regulations, guidance, advisories, and frameworks from NCSC.ch via any MCP-compatible client.6Apache 2.0