MCP.Market

Inforcer MCP server

by wyre-technology·io.github.wyre-technology/inforcer-mcp·v1.1.0·1 stars
No reviews yet

Read-only MCP server for Inforcer M365 baseline governance, plus assessment and report runs.

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Inforcer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Inforcer tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Inforcer compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Install Inforcer in Claude Code, Cursor or VS Code

claude mcp add inforcer-mcp -- docker run -i --rm ghcr.io/wyre-technology/inforcer-mcp:v1.1.0
Add to Cursor

What the publisher says

From the Inforcer repository's README, as published. We do not edit it. Read it on GitHub

Inforcer MCP Server

A Model Context Protocol (MCP) server that gives AI assistants structured, mostly read-only access to Inforcer Microsoft 365 baseline-governance data — tenants, baselines, alignment/drift, policies, secure scores, identity, audit logs, and report generation — plus two write actions to trigger an assessment run or queue a report.

Note: This project is maintained by Wyre Technology.

⚠ Community-sourced API

Inforcer does not (at time of writing) publish an official REST API specification. This server wraps the @wyre-technology/node-inforcer SDK, whose API surface is community-sourced from royklo/InforcerCommunity. Endpoints, field shapes, and behavior may change without notice. Treat results accordingly and verify anything load-bearing against the Inforcer portal.

Read-only scope

Every tool in this server is read-only EXCEPT two:

  • inforcerassessmentsrun — triggers an assessment run for a tenant.
  • inforcerreportsrun — queues one or more report runs across one or more tenants.

Both are HIGH-IMPACT (not destructive): they kick off real work in Inforcer and are visible to operators. Both are annotated accordingly and ask for confirmation before running. Confirm with the user before invoking.

There are no create/update/delete tools for policies, tenants, or baselines — those operations are not exposed by the community API and are intentionally absent here.

Quick Start

Claude Code (CLI):

claude mcp add inforcer-mcp \
  -e INFORCER_REGION=us \
  -e INFORCER_API_KEY=your-api-key \
  -- npx -y github:WYRE-AI/inforcer-mcp

See Installation for Docker and from-source methods.

Features

  • 🔌 MCP Protocol Compliance: Full support for MCP tools and prompts
  • 🛡️ Governance Coverage (read-only): Tenants, baselines, alignment/drift, policies, Microsoft Secure Score, Entra ID identity, and the audit log
  • 🔍 Decision-Tree Navigation: Start with inforcer_navigate to explore domains, then call domain-specific tools
  • 🧭 Flexible Tenant Resolution: Most tools accept a tenant as a numeric Client Tenant ID, a tenant DNS name, an Azure AD GUID, or a friendly name — resolved automatically
  • 🔒 Secure Authentication: Inf-Api-Key header auth, region-scoped
  • 🌐 Dual Transport: stdio (local) and HTTP Streamable (gateway/Docker)
  • 🐳 Docker Ready: Containerized deployment with HTTP transport and health checks
  • 📊 Structured Logging: Configurable levels, credentials never logged

Table of Contents

  • Installation
  • Configuration
  • Tenant identifiers
  • Domains and tools
  • Gateway connection
  • Docker Deployment
  • Development
  • Testing
  • Contributing
  • License

Installation

Option 1: Claude Code (CLI)

claude mcp add inforcer-mcp \
  -e INFORCER_REGION=us \
  -e INFORCER_API_KEY=your-api-key \
  -- npx -y github:WYRE-AI/inforcer-mcp

Option 2: Docker

docker compose up

Or pull the pre-built image:

docker run -d \
  -e INFORCER_REGION=us \
  -e INFORCER_API_KEY=your-key \
  -p 8080:8080 \
  ghcr.io/wyre-ai/inforcer-mcp:latest

Option 3: From Source

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Inforcer: common questions

Is Inforcer MCP server safe?
Mostly: it is graded B (75/100). Read the Inforcer safety report
How do I install Inforcer?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Inforcer need an API key?
Yes. The registry entry asks for INFORCER_API_KEY.
Is Inforcer maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v1.1.0.
How does Inforcer compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.

More from wyre-technology →