# L50 Microsoft Fix (remote · microsoft.l50automation.com)

Diagnose Windows, Microsoft 365, Entra, Intune and Azure errors: codes, fixes, outages, tenants.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `microsoft.l50automation.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/lewisororke-l50-microsoft-fix/microsoft.md), [page](https://verifymcp.io/servers/lewisororke-l50-microsoft-fix/microsoft)

## Channel facts

- Endpoint: `https://microsoft.l50automation.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1758 tokens (~159/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the L50 Microsoft Fix MCP server?

L50 Microsoft Fix is a hosted endpoint at https://microsoft.l50automation.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http lewisororke-l50-microsoft-fix 'https://microsoft.l50automation.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lewisororke-l50-microsoft-fix": {
      "url": "https://microsoft.l50automation.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lewisororke-l50-microsoft-fix": {
      "type": "http",
      "url": "https://microsoft.l50automation.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lewisororke-l50-microsoft-fix]
url = "https://microsoft.l50automation.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lewisororke-l50-microsoft-fix": {
      "type": "remote",
      "url": "https://microsoft.l50automation.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lewisororke-l50-microsoft-fix --url 'https://microsoft.l50automation.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lewisororke-l50-microsoft-fix:
    url: "https://microsoft.l50automation.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lewisororke-l50-microsoft-fix": {
      "Transport": "http",
      "Url": "https://microsoft.l50automation.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lewisororke-l50-microsoft-fix -t streamable-http -u 'https://microsoft.l50automation.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lewisororke-l50-microsoft-fix": {
      "type": "http",
      "url": "https://microsoft.l50automation.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 69)

First indexed and scored.

## MCP tools (11)

### `microsoft_diagnose` (~229 tokens)

microsoft diagnose

Diagnose any Microsoft problem from pasted text (error dialog, log lines, or a description): decodes every error code in it (Win32, HRESULT, NTSTATUS, blue screen, Entra AADSTS, Windows Update, CBS, MSI, Event IDs), finds the matching Microsoft support articles and live Microsoft Learn docs, and returns the likely cause, ranked fix steps with citations, commands labelled read-only or changes-the-system, a Microsoft outage check, Windows known issues for the version/KB, and which tenant tool to run next. Structured JSON for your AI to explain. Costs $0.02 per call, paid in USDC on Base with x402.

Input parameters:

- `product` (string): Optional product hint: windows, entra, intune, outlook, teams, office, azure
- `text` (string, required): The error message, code, log lines or problem description (up to 4000 characters)
- `windows_version` (string): Optional Windows version, e.g. '11 24H2' or 'Server 2022' (auto-detected from text)

### `microsoft_code` (~157 tokens)

microsoft code

Decode one Microsoft error code: 0x80070005, -2147024891, 80070002, C0000005, AADSTS50076, stop code 0x7E, ERROR_ACCESS_DENIED, Event ID 41, or 1603. Returns every family it belongs to (Win32, HRESULT with facility breakdown, NTSTATUS, bug check, AADSTS, Windows Update, CBS, BITS, WinInet, MSI, Event ID), the official meaning and the Microsoft reference link. 9,000+ codes. Costs $0.015 per call, paid in USDC on Base with x402.

Input parameters:

- `code` (string, required): The code, name or short text containing it

### `microsoft_search` (~127 tokens)

microsoft search

Search 6,000+ Microsoft support (troubleshooting) articles plus live Microsoft Learn docs for a problem. Error codes in the query are matched exactly. Each result has the summary, cause, fix steps, labelled commands and link. Costs $0.015 per call, paid in USDC on Base with x402.

Input parameters:

- `live` (boolean): Also search Microsoft Learn live (default true)
- `product` (string): Optional: windows-client, windows-server, azure, entra, mem (Intune), sql, ...
- `query` (string, required): Problem description or error code

### `microsoft_outage` (~102 tokens)

microsoft outage

Is it Microsoft's fault? Live Microsoft 365 and Azure public incident feeds, plus open Windows known issues for a Windows version. For incidents inside one tenant use microsoft_tenant_health. Costs $0.015 per call, paid in USDC on Base with x402.

Input parameters:

- `windows_version` (string): Optional Windows version for its open known issues, e.g. '11 24H2', '10 22H2', 'Server 2025'

### `microsoft_windows_issues` (~135 tokens)

microsoft windows issues

Windows known issues from Microsoft release health for a Windows version or a KB update: issue title, status (confirmed, mitigated, resolved), originating build and KB, last update and link. Covers Windows 11, Windows 10 and Windows Server 2016 to 2025. Costs $0.015 per call, paid in USDC on Base with x402.

Input parameters:

- `kb` (string): Update KB number, e.g. KB5124008
- `version` (string): Windows version, e.g. '11 24H2', '10 22H2', 'Server 2022'

### `microsoft_escalation` (~144 tokens)

microsoft escalation

Escalation pack: a ready-to-paste Microsoft support ticket or MSP escalation from the problem text, with decoded error codes, correlation/request IDs and timestamps pulled from the text, steps already tried, current Microsoft service status and the relevant Microsoft articles. Costs $0.015 per call, paid in USDC on Base with x402.

Input parameters:

- `environment` (string): Optional key=value pairs separated by ';', e.g. 'Windows=11 24H2;Office=Microsoft 365 Apps 2410'
- `steps_tried` (string): Steps already tried, separated by ';'
- `text` (string, required): Problem description, error text or logs

### `microsoft_tenant_signins` (~206 tokens)

microsoft tenant signins

Why can't this user sign in? Reads the user's recent Microsoft Entra sign-ins in YOUR tenant (with your read-only Graph token) and returns each failure decoded (AADSTS meaning), the Conditional Access policy that blocked it and what it required, app, device compliance, location and correlation ID, grouped into findings with fixes. Needs AuditLog.Read.All and Entra ID P1/P2. Token never stored. Costs $0.05 per call, paid in USDC on Base with x402.

Input parameters:

- `days` (integer): How many days back (default 3)
- `graph_token` (string): MCP only: your Microsoft Graph access token (read-only app registration; see https://microsoft.l50automation.com/microsoft/tenant-setup). Over HTTP send it as the 'Authorization: Bearer' header inste…
- `user` (string, required): User sign-in name (user@domain) or object ID

### `microsoft_tenant_health` (~162 tokens)

microsoft tenant health

Microsoft 365 service health inside YOUR tenant (with your read-only Graph token): degraded services and every open incident or advisory with impact, status and timestamps, optionally for one service (Exchange, Teams, SharePoint...). Needs ServiceHealth.Read.All. Token never stored. Costs $0.02 per call, paid in USDC on Base with x402.

Input parameters:

- `graph_token` (string): MCP only: your Microsoft Graph access token (read-only app registration; see https://microsoft.l50automation.com/microsoft/tenant-setup). Over HTTP send it as the 'Authorization: Bearer' header inste…
- `service` (string): Optional service name filter, e.g. Exchange, Teams, SharePoint

### `microsoft_tenant_user` (~182 tokens)

microsoft tenant user

Check one user in YOUR tenant (with your read-only Graph token): account blocked, missing licence or disabled service plan (Exchange, Teams, SharePoint, Intune), usage location, Intune device compliance and last check-in, and MFA methods registered, as findings with fixes. Needs User.Read.All (Intune and MFA checks need extra read scopes). Token never stored. Costs $0.05 per call, paid in USDC on Base with x402.

Input parameters:

- `graph_token` (string): MCP only: your Microsoft Graph access token (read-only app registration; see https://microsoft.l50automation.com/microsoft/tenant-setup). Over HTTP send it as the 'Authorization: Bearer' header inste…
- `user` (string, required): User sign-in name (user@domain) or object ID

### `microsoft_sample` (~55 tokens)

microsoft sample

Free: three worked Microsoft error diagnoses (Windows Update 0x800f0922, Entra AADSTS53003, blue screen 0x9F) showing what microsoft_diagnose returns. Try before you pay.

### `microsoft_tenant_setup` (~38 tokens)

microsoft tenant setup

Free: how to create the read-only Microsoft Graph token the tenant tools need (permissions, steps, PowerShell), and the privacy terms.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lewisororke-l50-microsoft-fix/microsoft#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 69

## Common questions

### What is the L50 Microsoft Fix MCP server?

L50 Microsoft Fix is an MCP server listed in the public MCP registry as io.github.lewisororke/l50-microsoft-fix. Diagnose Windows, Microsoft 365, Entra, Intune and Azure errors: codes, fixes, outages, tenants. This page covers its hosted endpoint (https://microsoft.l50automation.com/mcp).

### Is the L50 Microsoft Fix MCP server safe to use?

L50 Microsoft Fix scores 72 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 L50 Microsoft Fix MCP server expose?

L50 Microsoft Fix exposes 11 tools: microsoft_diagnose, microsoft_code, microsoft_search, microsoft_outage, microsoft_windows_issues, and 6 more. Their descriptions and schemas cost roughly 1,537 tokens of context every time the server is loaded.

### Does the L50 Microsoft Fix MCP server require authentication?

No. We connected to L50 Microsoft Fix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the L50 Microsoft Fix MCP server still maintained?

L50 Microsoft Fix is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the L50 Microsoft Fix MCP server?

VerifyMCP ran 13 checks on L50 Microsoft Fix, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://microsoft.l50automation.com/mcp
- Website: https://microsoft.l50automation.com/
- Changelog RSS feed: https://verifymcp.io/servers/lewisororke-l50-microsoft-fix/microsoft.xml
- Changelog JSON feed: https://verifymcp.io/servers/lewisororke-l50-microsoft-fix/microsoft/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lewisororke-l50-microsoft-fix/microsoft.json
- HTML version of this page: https://verifymcp.io/servers/lewisororke-l50-microsoft-fix/microsoft
