Mcp Defender

io.github.trickyfalconPublished by GitHub account trickyfalconv0.1.0Updated Oct 24, 2026

Execute KQL queries against Microsoft Defender Advanced Hunting via natural language.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant run KQL queries against Microsoft Defender Advanced Hunting from natural language requests.

What you can do
This local MCP server connects an assistant to Microsoft Defender Advanced Hunting so it can execute KQL queries. The registry description states it translates natural language into those queries, letting the assistant retrieve hunting data without the user writing KQL by hand. No individual tools are listed in the manifest.
When to use it
Worth adding when you work with Microsoft Defender Advanced Hunting and want an assistant to query that data conversationally instead of writing KQL yourself. It is a desktop-only local process, so it suits individual analyst workstations rather than shared or browser-based setups.
Requirements
Runs as a local stdio process on the user's machine, installed from the PyPI package mcp-defender, so a Python runtime is needed. The manifest declares no authentication, environment variables, or headers, but connecting to Microsoft Defender Advanced Hunting normally requires access to that service; the input does not specify how credentials are supplied.
Before you install
The manifest declares no authentication and no environment variables, so how the server obtains access to Microsoft Defender Advanced Hunting is not documented here. Queries read tenant security data, which is sensitive; review what data leaves your environment before installing. No write, delete, or payment behavior is described in the input.

Installation

In SourceWeft

  1. Open Mcp Defender in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.