Inforcer
OCI · GHCR.IO/WYRE-AI/INFORCER-MCP:V1.1.2 · SCANNED SEP 20
Read-only MCP server for Inforcer M365 baseline governance, plus assessment and report runs.
Available components
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 → Why this is hard to 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 23 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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
How do I install the Inforcer MCP server?
Inforcer runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/inforcer-mcp:v1.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-ai/inforcer-mcp:v1.1.2
claude mcp add wyre-ai-inforcer-mcp -- docker run --rm -i ghcr.io/wyre-ai/inforcer-mcp:v1.1.2
{
"mcpServers": {
"wyre-ai-inforcer-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/inforcer-mcp:v1.1.2"
]
}
}
} {
"servers": {
"wyre-ai-inforcer-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/inforcer-mcp:v1.1.2"
]
}
}
} codex mcp add wyre-ai-inforcer-mcp -- docker run --rm -i ghcr.io/wyre-ai/inforcer-mcp:v1.1.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wyre-ai-inforcer-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/inforcer-mcp:v1.1.2"
],
"enabled": true
}
}
} mcp_servers:
wyre-ai-inforcer-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/inforcer-mcp:v1.1.2"] {
"McpServers": {
"wyre-ai-inforcer-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/inforcer-mcp:v1.1.2"
]
}
}
} {
"mcpServers": {
"wyre-ai-inforcer-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/inforcer-mcp:v1.1.2"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
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 20 Sept 2026 · Analysed oci/ghcr.io/wyre-ai/inforcer-mcp:v1.1.2
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 |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| 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 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 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.
| 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 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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 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 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.
| 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.
| 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 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.
| 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 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.
| 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.
| 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.
| 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.
What is the Inforcer MCP server?
Inforcer is an MCP server listed in the public MCP registry as io.github.WYRE-AI/inforcer-mcp. Read-only MCP server for Inforcer M365 baseline governance, plus assessment and report runs. This page covers its container image (ghcr.io/wyre-ai/inforcer-mcp:v1.1.2).
Is the Inforcer MCP server safe to use?
Inforcer scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Inforcer MCP server expose?
Inforcer exposes 24 tools: inforcer_navigate, inforcer_status, inforcer_tenants_list, inforcer_tenants_get, inforcer_tenants_resolve, and 19 more. Their descriptions and schemas cost roughly 2,187 tokens of context every time the server is loaded.
Is the Inforcer MCP server still maintained?
Inforcer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Inforcer MCP server under?
Inforcer declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.