Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Microsoft MCP Server for Enterprise

REMOTE · MCP.SVC.CLOUD.MICROSOFT · SCANNED SEP 20

Official Microsoft MCP Server to query Microsoft Entra data using natural language

0 this week 40 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security100
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the Microsoft MCP Server for Enterprise server?

Microsoft MCP Server for Enterprise is a hosted endpoint at https://mcp.svc.cloud.microsoft/enterprise, 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.

remote · mcp.svc.cloud.microsoft

# add to Claude Code
claude mcp add --transport http microsoft-enterprisemcp 'https://mcp.svc.cloud.microsoft/enterprise'
// .cursor/mcp.json
{
  "mcpServers": {
    "microsoft-enterprisemcp": {
      "url": "https://mcp.svc.cloud.microsoft/enterprise"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "microsoft-enterprisemcp": {
      "type": "http",
      "url": "https://mcp.svc.cloud.microsoft/enterprise"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.microsoft-enterprisemcp]
url = "https://mcp.svc.cloud.microsoft/enterprise"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "microsoft-enterprisemcp": {
      "type": "remote",
      "url": "https://mcp.svc.cloud.microsoft/enterprise",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add microsoft-enterprisemcp --url 'https://mcp.svc.cloud.microsoft/enterprise' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  microsoft-enterprisemcp:
    url: "https://mcp.svc.cloud.microsoft/enterprise"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "microsoft-enterprisemcp": {
      "Transport": "http",
      "Url": "https://mcp.svc.cloud.microsoft/enterprise"
    }
  }
}
# add to Vellum
assistant mcp add microsoft-enterprisemcp -t streamable-http -u 'https://mcp.svc.cloud.microsoft/enterprise'
// mcp.json
{
  "mcpServers": {
    "microsoft-enterprisemcp": {
      "type": "http",
      "url": "https://mcp.svc.cloud.microsoft/enterprise"
    }
  }
}

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

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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    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 20 Sept 2026 · Probed https://mcp.svc.cloud.microsoft/enterprise

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.svc.cloud.microsoft,O=Microsoft Corporation,L=Redmond,ST=WA,C=US CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US 8 Sept 2026 7 Mar 2027 RSA 2048 SHA384-RSA 430101554300c76091f2c127fc000001015543
SANs: *.fabriciq.svc.cloud.dev.microsoft, *.iq.svc.cloud.dev.microsoft, *.mcp.svc.cloud.dev.microsoft, *.safeai.svc.cloud.dev.microsoft, *.safeai.svc.cloud.microsoft, *.workiq.svc.cloud.dev.microsoft, fabriciq.svc.cloud.microsoft, iq.svc.cloud.microsoft, mcp.svc.cloud.microsoft, workiq.svc.cloud.microsoft
CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US (CA) CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US 1 Aug 2025 3 Jun 2029 RSA 4096 SHA384-RSA 330000000b13e5667d4a9b558000000000000b
CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 21 May 2025 19 Jun 2029 RSA 4096 SHA384-RSA b0c6b2c466917b04773c647d4afc0c8

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.svc.cloud.microsoft. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
microsoft. present 55012 8 Verified
cloud.microsoft. present 61899 13 Verified
mcp.svc.cloud.microsoft. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer realm="", authorization_uri="https://login.microsoftonline.com/common/oauth2/authorize", client_id="e8c77dc2-69b3-43f4-bc51-3213c9d915b4", resource_metadata="https://mcp.svc.cloud.microsoft/.well-known/oauth-protected-resource/enterprise"

Bearer realm="", authorization_uri="https://login.microsoftonline.com/common/oauth2/authorize", client_id="e8c77dc2-69b3-43f4-bc51-3213c9d915b4", resource_metadata="https://mcp.svc.cloud.microsoft/.well-known/oauth-protected-resource/enterprise"
Header Value
strict-transport-security max-age=31536000
www-authenticate Bearer realm="", authorization_uri="https://login.microsoftonline.com/common/oauth2/authorize", client_id="e8c77dc2-69b3-43f4-bc51-3213c9d915b4", resource_metadata="https://mcp.svc.cloud.microsoft/.well-known/oauth-protected-resource/enterprise"

Protected resource metadata

Document https://mcp.svc.cloud.microsoft/.well-known/oauth-protected-resource/enterprise
Retrieved Yes
Resource https://mcp.svc.cloud.microsoft/enterprise
Authorisation server https://login.microsoftonline.com/organizations/v2.0

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.svc.cloud.microsoft/enterprise Auth required 401
http (plaintext) http://mcp.svc.cloud.microsoft/enterprise HTTPS enforced 308 https://mcp.svc.cloud.microsoft/enterprise
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the Microsoft MCP Server for Enterprise server?

Microsoft MCP Server for Enterprise is listed in the public MCP registry as io.github.microsoft/EnterpriseMCP. Official Microsoft MCP Server to query Microsoft Entra data using natural language. This page covers its hosted endpoint (https://mcp.svc.cloud.microsoft/enterprise).

Is the Microsoft MCP Server for Enterprise server safe to use?

Microsoft MCP Server for Enterprise scores 40 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.

Does the Microsoft MCP Server for Enterprise server require authentication?

Yes. Microsoft MCP Server for Enterprise asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Microsoft MCP Server for Enterprise server still maintained?

Microsoft MCP Server for Enterprise 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.