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.

Intune Ready

REMOTE · INTUNEREADY.COM · SCANNED SEP 27

Fixed-price Microsoft Intune and Windows 365 setup for small businesses: tiers, scope, FAQ, facts.

Available components

69 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 Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 706 tokens (~117/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Intune Ready MCP server?

Intune Ready is a hosted endpoint at https://intuneready.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.

remote · intuneready.com

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

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 Sept 26 +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.

  • 25 Sept 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
  • 24 Sept 26 +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.

  • 22 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 21 Sept 26 66

    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 27 Sept 2026 · Probed https://intuneready.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=intuneready.com CN=YE2,O=Let's Encrypt,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA384 568055ee4c7c57186062941ce1ac6ece129
SANs: *.intuneready.com, intuneready.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of intuneready.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
intuneready.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://intuneready.com/mcp Verified 200
http (plaintext) http://intuneready.com/mcp HTTPS enforced 301 https://intuneready.com/mcp
MCP tools · 6 exposed · ~614 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. 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 →

Tool Tokens
get_cloud_pc_offering ~130

Returns the Cloud PC service line, which is separate from the Intune service: Windows 365 implementation (the primary service, with fixed-price setup tiers by number of users) and Azure Virtual Desktop implementation (for larger and multi-location teams, custom quote only). Also covers how the two compare. Microsoft license prices are never included. Use this for questions about Cloud PCs, Windows 365, Azure Virtual Desktop, or replacing physical PCs.

NameTypeReqDescription
sectionstring–Which part to return. Defaults to "all".
servicestring–Which service to return. Defaults to "all".

No output schema declared.

No examples provided.

get_contact ~43

Returns the URL where a human can start a conversation or book a free consultation. This is a pointer only — this server cannot book, schedule, quote, or transact anything.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_facts ~90

Returns verifiable facts about the provider: background, Microsoft Partner Program membership, active certifications, the hands-on delivery record for Windows 365 and Azure Virtual Desktop, and public company and personal profile links (LinkedIn, Google Business Profile, Microsoft Learn). Use this for questions about qualifications, credentials, or who does the work.

NameTypeReqDescription
topicstring–Which facts to return. Defaults to "all".

No output schema declared.

No examples provided.

get_faq ~117

Returns the general Intune Ready FAQ from the homepage, verbatim: licensing, cost, timelines, messy existing enrollments, and what happens after setup. Optionally filter with a search term to return only matching pairs. It does not cover the other published FAQs — use get_partner_channel for MSPs and independent IT contractors, and get_cloud_pc_offering for Windows 365 and Azure Virtual Desktop. If nothing matches, says so rather than guessing.

NameTypeReqDescription
querystring–Optional case-insensitive search term matched against questions and answers.

No output schema declared.

No examples provided.

get_offering ~89

Returns what Intune Ready offers: the three fixed-price tiers with hour and cost ranges, the billing model, what a deployment covers, and the service area. Figures are indicative ranges published on the site, not a quote. Use this for questions about price, scope, tiers, or what is included.

NameTypeReqDescription
sectionstring–Which part of the offering to return. Defaults to "all".

No output schema declared.

No examples provided.

get_partner_channel ~145

Returns how Intune Ready takes on work through partners: MSPs routing overflow, specialty or rescue Intune projects, and independent IT contractors subcontracting or referring a client. Covers the arrangements, what stays with the partner, and the client-ownership commitment. Carries no prices of its own — a partner engagement is priced from the tiers in get_offering. Use this for questions about subcontracting Intune work, white-label delivery, referring a client, or hiring an Intune specialist as an MSP or contractor.

NameTypeReqDescription
audiencestring–Which partner audience to return. Defaults to "all".
sectionstring–Which part to return. Defaults to "all".

No output schema declared.

No examples provided.

Common questions

What is the Intune Ready MCP server?

Intune Ready is an MCP server listed in the public MCP registry as com.intuneready/intune-ready. Fixed-price Microsoft Intune and Windows 365 setup for small businesses: tiers, scope, FAQ, facts. This page covers its hosted endpoint (https://intuneready.com/mcp).

Is the Intune Ready MCP server safe to use?

Intune Ready scores 69 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 Intune Ready MCP server expose?

Intune Ready exposes 6 tools: get_offering, get_cloud_pc_offering, get_partner_channel, get_faq, get_facts, get_contact. Their descriptions and schemas cost roughly 614 tokens of context every time the server is loaded.

Does the Intune Ready MCP server require authentication?

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

Is the Intune Ready MCP server still maintained?

Intune Ready is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.