Two weeks after shipping eight Agent365 servers that scored between 20 and 32, Microsoft is back with nine more. The WorkIQ suite covers Outlook mail, Calendar, Teams, SharePoint Lists, OneDrive/SharePoint files, Word, admin tools, a “me server” (user profile), and an M365 Copilot bridge. All nine score 32.
What WorkIQ Covers
| Server | Function | Score |
|---|---|---|
workiq-mailtools | Outlook mail operations | 32 |
workiq-calendartools | Calendar management | 32 |
workiq-teamsserver | Microsoft Teams | 32 |
workiq-sharepointliststools | SharePoint Lists | 32 |
workiq-odspremoteserver | OneDrive/SharePoint files | 32 |
workiq-wordserver | Word document operations | 32 |
workiq-admintools | Admin tools | 32 |
workiq-meserver | User profile / me endpoint | 32 |
workiq-m365copilot | M365 Copilot bridge | 32 |
Why 32?
The scoring breakdown is familiar from the Agent365 batch. All nine servers point to a repository at github.com/bap-microsoft/MCP-Platform/ — a personal-looking GitHub account rather than the official github.com/microsoft/mcp organization. No license declared. No installable packages. Zero secrets required (which helps the permissions score), but no community signals — no stars, no forks, no contributor activity visible to our enrichment pipeline.
For context, Microsoft’s official MCP servers — azure, microsoft-fabric, and template-server-name — all score 88. Those live in the github.com/microsoft/mcp repo with 2,880 stars, 436 forks, and proper licensing. The gap between Microsoft’s official and experimental registrations is 56 points.
The Pattern
Microsoft now has 17 servers in the registry. Eight score 88 (the official suite). Eight score 20–32 (Agent365). Nine score 32 (WorkIQ). The company is using the MCP registry as a staging ground for experimental integrations, publishing them under the com.microsoft namespace but pointing to personal or team repos rather than the official organization.
This is not inherently problematic — companies explore in public all the time. But it does create confusion in the registry. A user searching for Microsoft MCP servers sees 17 results with trust scores ranging from 20 to 88, with no obvious way to distinguish official from experimental without clicking through to the source repo.
The WorkIQ suite covers the full M365 productivity stack. If these mature into officially-supported servers hosted in the microsoft/mcp organization with proper licensing and packages, they could become some of the most consequential MCP integrations in the registry. Microsoft 365 has over 400 million paid seats. An MCP bridge to Outlook, Teams, and SharePoint is not a niche play — it is infrastructure.
For now, treat these as what they are: early-stage experiments from a team inside Microsoft, published under the company namespace but not yet meeting the company’s own quality bar.