What is the key difference between Haldir and Inforcer?

Haldir belongs to the Security category with local stdio execution, while Inforcer belongs to the Security category with local stdio execution.

How do I install Haldir or Inforcer in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Haldir and Inforcer free or paid?

Haldir operates under a Freemium model (API Key required). Inforcer operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Haldir lists 6 tools with 3 views and 4 GitHub stars. Inforcer lists 6 tools with 1 views and 1 GitHub stars.

Can I use both Haldir and Inforcer together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Haldir vs Inforcer

In-depth architectural comparison of the Haldir and Inforcer MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Haldir

Security · Local stdio

Quality: 41/100 (Fair) | Auth: API Key required

Inforcer

Security · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Haldir if you need specialized Security tools running via a local process. Choose Inforcer if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Haldir when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: HALDIR_ENCRYPTION_KEY.
Primary tools included: Scoped agent sessions, AES-256-GCM encrypted secret vault, Hash-chained audit trail.

Explore Haldir Details

Choose Inforcer when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: INFORCER_REGION, INFORCER_API_KEY.
Primary tools included: Read-only Microsoft 365 governance queries, Tenant identifier resolution across multiple input formats, Baseline alignment and drift inspection.

Feature & Specification Comparison

Specification	Haldir Security	Inforcer Security
Summary	Guardian layer for AI agents: identity, secrets, audit via MCP.	Read-only MCP server for Inforcer M365 baseline governance, plus assessment runs.
Category & Scope	Security	Security
Quality signal

Tools & Capabilities Breakdown

Haldir Tools (6)

Scoped agent sessions

AES-256-GCM encrypted secret vault

Hash-chained audit trail

Human approval workflows

MCP call interception proxy

Compliance evidence exports

Inforcer Tools (6)

Read-only Microsoft 365 governance queries

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Haldir Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "haldir": {
      "command": "uvx",
      "args": [
        "haldir"
      ],
      "env": {
        "HALDIR_ENCRYPTION_KEY": "YOUR_HALDIR_ENCRYPTION_KEY_HERE"
      }
    }
  }
}

Inforcer Configuration