AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
MCP verified MIT Self-run

Defender MCP

mcp-menkw-defender-mcp · by MenkW

MCP server for Microsoft Defender XDR — incidents, alerts, machines, advanced hunting, and threat intelligence for AI assistants

— No reviews yet
0 installs
29 views
0.0% view→install

Install

$ agentstack add mcp-menkw-defender-mcp

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ● Environment & secrets Used
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/mcp-menkw-defender-mcp)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 5mo ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Defender MCP? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Defender-MCP

A Model Context Protocol (MCP) server for Microsoft Defender XDR and Microsoft Defender for Endpoint. Enables AI assistants (Claude, Kilo, etc.) to interact with your security environment using natural language — investigating incidents, hunting threats, managing devices, and querying vulnerabilities.

Features

  • ~45 tools across 9 security categories
  • Dual-token authentication — separate Azure AD tokens for the MTP API (api.security.microsoft.com) and the WDATP API (api.securitycenter.microsoft.com)
  • XDR cross-workload hunting — query endpoint, identity, email, and cloud app data in a single KQL query
  • Incident management — list, get, update incidents with full alert and evidence detail
  • Device response actions — isolate machines, run AV scans, collect investigation packages, execute live response
  • Threat intelligence — create, import, and manage IOC indicators (file hashes, IPs, domains, URLs)
  • Vulnerability management — CVE lookup, software inventory, security recommendations, remediation tracking

Tool Categories

| Category | Tools | Description | |---|---|---| | Incidents | 4 | List, get, get alerts, update incidents | | Alerts | 5 | List, get, update, batch-update, create alerts | | Machines | 16 | Get devices, isolate, AV scan, restrict code execution, live response | | Advanced Hunting | 2 | WDATP KQL query + XDR cross-workload KQL query | | Entities | 11 | File hashes, domains, IPs, user alerts and machines | | Indicators (IoC) | 5 | Get, create, import, delete threat indicators | | Machine Actions | 12 | Investigation packages, live response, automated investigations | | Scoring | 5 | Exposure score, secure score, AV health, device health | | Vulnerabilities | 17 | CVEs, software inventory, recommendations, remediation activities |

Prerequisites

  • Node.js 18.0.0 or higher
  • Azure AD App Registration (Microsoft Entra ID) with the following API permissions granted as Application permissions (not delegated):

Required API Permissions

api.security.microsoft.com (Microsoft Threat Protection):

  • AdvancedHunting.Read.All
  • Incident.Read.All
  • Incident.ReadWrite.All

WindowsDefenderATP (Microsoft Defender for Endpoint):

  • Alert.Read.All
  • Alert.ReadWrite.All
  • Machine.Read.All
  • Machine.ReadWrite.All
  • Machine.Isolate
  • Machine.LiveResponse
  • Machine.Scan
  • Ti.Read.All
  • Ti.ReadWrite.All
  • Vulnerability.Read.All
  • Software.Read.All
  • Score.Read.All
  • SecurityRecommendation.Read.All

> Important: All permissions must be Application type and require admin consent.

Setup

  1. Clone the repository:

``bash git clone https://github.com/MenkW/Defender-MCP.git cd Defender-MCP ``

  1. Install dependencies:

``bash npm install ``

  1. Configure credentials:

``bash cp .env.example .env ` Edit .env and fill in your Azure AD app registration details: `env DEFENDER_TENANT_ID=your-tenant-id DEFENDER_CLIENT_ID=your-client-id DEFENDER_CLIENT_SECRET=your-client-secret ``

  1. Build:

``bash npm run build ``

MCP Configuration

Add to your MCP client config (e.g., Kilo kilo.json or Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "defender": {
      "command": "node",
      "args": ["C:/path/to/Defender-MCP/dist/index.js"],
      "env": {
        "DEFENDER_TENANT_ID": "your-tenant-id",
        "DEFENDER_CLIENT_ID": "your-client-id",
        "DEFENDER_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Or if you use a .env file and have it populated:

{
  "mcpServers": {
    "defender": {
      "command": "node",
      "args": ["C:/path/to/Defender-MCP/dist/index.js"]
    }
  }
}

Architecture

src/
  index.ts              # MCP server entrypoint -- loads all tool modules
  auth.ts               # Dual-token MSAL authentication (MTP + WDATP scopes)
  api-client.ts         # HTTP client -- routes requests to correct API + token
  tools/
    incidents.ts        # Incident management tools
    alerts.ts           # Alert tools
    machines.ts         # Device/machine tools including response actions
    advanced-hunting.ts # KQL hunting (WDATP and XDR)
    entities.ts         # File, IP, domain, user enrichment
    indicators.ts       # Threat intelligence / IoC management
    machine-actions.ts  # Investigation packages, live response, investigations
    scoring.ts          # Exposure score, secure score, AV health
    vulnerabilities.ts  # CVE, software, recommendations, remediation

Authentication Architecture

The server uses two separate Azure AD token acquisition flows:

  • MTP token -- scope https://api.security.microsoft.com/.default -- used for Incidents and XDR Advanced Hunting
  • WDATP token -- scope https://api.securitycenter.microsoft.com/.default -- used for Alerts, Machines, Indicators, Vulnerabilities, etc.

Both tokens are cached per-scope and automatically refreshed by MSAL.

Development

# Run directly with tsx (no build required)
npm run dev

# Build TypeScript to dist/
npm run build

# Run built output
npm start

License

MIT -- see [LICENSE](LICENSE) for details.

Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.