Muster.

developers

API changelog

What's new in the REST API and MCP server. The API is additive — new fields and endpoints show up here, and we won't remove or rename anything you depend on without notice.

ℹ
Response objects may gain new fields at any time. Write clients that ignore unknown fields, and you'll never break on an addition.

August 12, 2026

latest
  • Breaking: the engine field and filter now use generic tokens — code, web, deps, cloud, dns, contract — on GET /orgs/:id/scans, GET /scans/:id, findings, and the list_findings MCP tool. Update any code that filtered or branched on the old values.

August 11, 2026

  • GitHub issues from findings. On a finding that's on a connected GitHub repo, click Create GitHub issue to open an issue in that repo with the finding's details and a link back — the remediation hand-off. Idempotent (a second click returns the existing issue).
  • Scan events in Slack/Teams. Chat channels can now opt in to “scan completed” and “scan failed” messages (not just findings) — toggle them per channel under Settings → Notifications.
  • Weekly digest. A weekly email summarizing each org's security score, open findings by severity, and what changed that week (default on; toggle under Account → Notifications).
  • GitHub issues auto-close. When a finding is marked fixed — manually or by a re-scan that no longer detects it — Muster comments on and closes its linked GitHub issue.
  • Notification severity threshold. Each notification channel now honors a “notify on” threshold (default Medium and above) — set it when you add a Slack, Teams, or webhook channel so you only get paged for what matters.
  • Microsoft Teams. Send findings to a Teams channel alongside Slack — add a Teams channel under Integrations and paste the URL from a Power Automate “post to a channel when a webhook request is received” workflow.
  • Webhooks. Add a generic webhook channel under an org's Integrations to receive signed JSON events — scan.completed, scan.failed, findings.new, findings.regressed — at your own endpoint. Every request carries an X-Muster-Signature HMAC. See the webhook docs.
  • Scan emails. Muster now emails your org when a scan finishes or fails (default on; one email per scan). Manage it under Account → Notifications.
  • Every list endpoint now paginates the same way: limit (default 25, max 100) and offset, with count, total, and has_more in the response. This now covers GET /orgs/:id/assets and GET /orgs/:id/scans (previously unpaginated / limit-only), plus the list_assets and list_scans MCP tools, which gained limit + offset.
  • Heads-up: the default page size for GET /orgs/:id/findings changed from 100 to 25 (max is now 100). Pass limit explicitly for larger pages.

August 2, 2026

  • Scan a specific asset: POST /orgs/:id/scan now accepts asset_ids (and the trigger_scan MCP tool). Previously scans were org-level only.

August 1, 2026

  • Findings now return exploitable, original_severity, impact, remediation, the linked asset, a deep-link url, and updated_at.
  • List findings gained type and updated_since filters, plus offset pagination — responses now include total and has_more.
  • New endpoints: GET /orgs/:id/scans, GET /scans/:id, and GET /orgs/:id/summary.
  • PATCH /findings/:id accepts an optional note, recorded on the finding as an audit trail.
  • Hygiene: stable machine codes on every error, X-RateLimit-* headers, and Idempotency-Key support on POST /orgs/:id/scan.
  • MCP server added list_scans, get_scan, and get_summary tools; update_finding now takes a note.

July 2026

v1
  • Initial public API: /orgs, /orgs/:id/assets, /orgs/:id/findings, /findings/:id (GET + PATCH), and POST /orgs/:id/scan.
  • Org-scoped API keys that carry your role and stop working if you leave the org.
  • MCP server for Claude Code / Cursor: list, read, triage findings and trigger scans from your editor.

Have a field or endpoint you wish existed? Use Send feedback in the help menu — the roadmap is shaped by what teams actually reach for.