Inforcer

OCI · GHCR.IO/WYRE-TECHNOLOGY/INFORCER-MCP:V1.1.0 · SCANNED AUG 22

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

Available components

oci · ghcr.io/wyre-technology/inforcer-mcp:v1.1.0 39

39 39 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security0

Malware scan not yet available for this package.Unverified
Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Install-script risk not yet assessed.Unverified
Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified

Provenance & Transparency32

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
Actively maintained (last published 2 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability89

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 2187 tokens (~91/item across 24 items; 24 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/wyre-technology/inforcer-mcp:v1.1.0

Claude Codex opencode Hermes Other

# add to Claude Code

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

# add to Codex CLI

codex mcp add wyre-technology-inforcer-mcp -- docker run --rm -i ghcr.io/wyre-technology/inforcer-mcp:v1.1.0

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-technology-inforcer-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/inforcer-mcp:v1.1.0"
      ],
      "enabled": true
    }
  }
}

# ~/.hermes/config.yaml

mcp_servers:
  wyre-technology-inforcer-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/inforcer-mcp:v1.1.0"]

// mcp.json

{
  "mcpServers": {
    "wyre-technology-inforcer-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/inforcer-mcp:v1.1.0"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

19 Aug 26 39

First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Aug 2026 · Analysed oci/ghcr.io/wyre-technology/inforcer-mcp:v1.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	oci
Reason	No attestation published

MCP tools · 24 exposed · ~2,187 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

inforcer_alignment_details ~105

Get detailed baseline-alignment drift for a tenant. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

inforcer_alignment_scores ~20

List baseline alignment scores across tenants. Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inforcer_assessments_list ~28

List the assessments available to run (use to discover assessment IDs). Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inforcer_assessments_run ~160

⚠ HIGH-IMPACT. Triggers an assessment run for a tenant. This is not destructive, but it kicks off real work in Inforcer and is visible to operators. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Confirm with the user before invoking.

Input Output Examples

Name	Type	Req	Description
assessment_id	string	yes	The assessment ID to run (discover IDs via inforcer_assessments_list)
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

inforcer_audit_event_types ~27

List the audit event types available for filtering the activity log. Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inforcer_audit_search ~123

Search the Inforcer activity (audit) log. All filters are optional; returns a page of events plus a continuation token for paging. Read-only.

Input Output Examples

Name	Type	Req	Description
continuation_token	string	–	Pagination cursor from a prior page
date_from	string	–	ISO-8601 start of the date range
date_to	string	–	ISO-8601 end of the date range
event_types	array	–	Filter to these audit event types (see inforcer_audit_event_types)
page_size	number	–	Max events per page

No output schema declared.

No examples provided.

inforcer_baselines_list ~54

List baseline groups and their members. Optionally filter by the baseline (owner) tenant ID. Read-only.

Input Output Examples

Name	Type	Req	Description
baseline_tenant_id	number	–	Filter baseline groups by baseline (owner) Client Tenant ID

No output schema declared.

No examples provided.

inforcer_groups_get ~122

Get full detail for a single group, including members. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
group_id	string	yes	The group ID (Entra object ID)
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

inforcer_groups_list ~134

List Entra ID group summaries for a tenant (paginated). Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
continuation_token	string	–	Pagination cursor from a prior page
search	string	–	Filter groups by search term
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

inforcer_navigate ~187

Discover available Inforcer tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	The domain to explore: - tenants: list/get tenants, resolve a name/DNS/GUID to a Client Tenant ID - baselines: list baseline groups - alignment: alignment scores and per-tenant drift details - polici…

No output schema declared.

No examples provided.

inforcer_policies_list ~102

List policies for a tenant. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

inforcer_reports_download_output ~83

Download a single finished report output (discovered via inforcer_reports_run_status). Returns the file content base64-encoded along with its filename and content type. Read-only.

Input Output Examples

Name	Type	Req	Description
output_id	string	yes	The output's id, from inforcer_reports_run_status's outputs list.
run_id	string	yes	The run identifier the output belongs to.

No output schema declared.

No examples provided.

inforcer_reports_run ~162

⚠ HIGH-IMPACT. Queues one or more reports across one or more tenants. This is not destructive, but it kicks off real report-generation work in Inforcer. Reports run asynchronously — use inforcer_reports_run_status to poll the returned run(s) to completion, then inforcer_reports_download_output to fetch each finished output. Confirm with the user before invoking.

Input Output Examples

Name	Type	Req	Description
reports	array	yes	One or more reports to queue. Discover valid type/output_format pairs via inforcer_reports_types_list.
tenants	array	yes	Tenant identifiers to run the report(s) against — each accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to numeric Client Tenant IDs before…

No output schema declared.

No examples provided.

inforcer_reports_run_status ~65

Poll a report run. Returns isTerminal:false with no outputs while the run is still in progress, or isTerminal:true with the list of downloadable outputs once it finishes. Read-only.

Input Output Examples

Name	Type	Req	Description
run_id	string	yes	The run identifier returned by inforcer_reports_run.

No output schema declared.

No examples provided.

inforcer_reports_runs_list ~21

List queued and completed report runs. Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inforcer_reports_types_list ~63

List the catalog of available report types — key, supported output formats, whether the type is collatable (single cross-tenant output), and accepted parameters. Use to discover valid (type, output_format) pairs before calling inforcer_reports_run. Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inforcer_roles_list ~106

List Entra ID directory role definitions for a tenant. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

inforcer_secure_scores_get ~106

Get the Microsoft Secure Score data for a tenant. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

inforcer_status ~33

Check Inforcer API connectivity and available domains. Performs a live baselines.list() call as a read-only connectivity check.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inforcer_tenants_get ~117

Get a single tenant. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Ambiguous names throw a clear error. Read-only.

Input Output Examples

Name	Type	Req	Description
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Ambiguous names th…

No output schema declared.

No examples provided.

inforcer_tenants_list ~19

List all managed tenants. Read-only.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

inforcer_tenants_resolve ~97

Resolve a tenant name, DNS name, or Azure AD GUID to its numeric Inforcer Client Tenant ID (which is NOT the Azure AD tenant GUID). Read-only.

Input Output Examples

Name	Type	Req	Description
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Ambiguous names th…

No output schema declared.

No examples provided.

inforcer_users_get ~119

Get full detail for a single user. Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.
user_id	string	yes	The user ID (Entra object ID)

No output schema declared.

No examples provided.

inforcer_users_list ~134

List Entra ID user summaries for a tenant (paginated). Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request. Read-only.

Input Output Examples

Name	Type	Req	Description
continuation_token	string	–	Pagination cursor from a prior page
search	string	–	Filter users by search term
tenant	string	yes	Tenant identifier — accepts a numeric Client Tenant ID, a tenant DNS name, an Azure AD tenant GUID, or a friendly name. Resolved to the numeric Client Tenant ID before the request.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

19 Aug 22 Aug