Intune Ready
com.intuneready/intune-ready · 1.2.1
Fixed-price Microsoft Intune and Windows 365 setup for small businesses: tiers, scope, FAQ, facts.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://intuneready.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 6 tools.
- Protocol
- 2025-06-18
- Calls itself
- intuneready 1.2.1
- Handshake time
- 175 ms
- HTTP status
- 200
The tools it lists (6, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_offeringReturns 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.
get_cloud_pc_offeringReturns 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.
get_partner_channelReturns 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.
get_faqReturns 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.
get_factsReturns 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.intuneready/intune-ready, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 16 days ago. The registry entry · intuneready.com