M365 Roadmap
PYPI · M365-ROADMAP-MCP · SCANNED SEP 20
Query the Microsoft 365 Roadmap from AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 227 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1035 tokens (~1035/item across 1 items; 1 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 Management80
- Stability observed for 24 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the M365 Roadmap MCP server?
M365 Roadmap runs locally as a PyPI package, launched with uvx m365-roadmap-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · m365-roadmap-mcp
claude mcp add jonnybottles-m365-roadmap -- uvx m365-roadmap-mcp
{
"mcpServers": {
"jonnybottles-m365-roadmap": {
"command": "uvx",
"args": [
"m365-roadmap-mcp"
]
}
}
} {
"servers": {
"jonnybottles-m365-roadmap": {
"command": "uvx",
"args": [
"m365-roadmap-mcp"
]
}
}
} codex mcp add jonnybottles-m365-roadmap -- uvx m365-roadmap-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jonnybottles-m365-roadmap": {
"type": "local",
"command": [
"uvx",
"m365-roadmap-mcp"
],
"enabled": true
}
}
} openclaw mcp add jonnybottles-m365-roadmap --command uvx --arg m365-roadmap-mcp
mcp_servers:
jonnybottles-m365-roadmap:
command: "uvx"
args: ["m365-roadmap-mcp"] {
"McpServers": {
"jonnybottles-m365-roadmap": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"m365-roadmap-mcp"
]
}
}
} assistant mcp add jonnybottles-m365-roadmap -t stdio -c uvx -a m365-roadmap-mcp
{
"mcpServers": {
"jonnybottles-m365-roadmap": {
"command": "uvx",
"args": [
"m365-roadmap-mcp"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
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 · Analysed pypi/m365-roadmap-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
search_roadmap Search Roadmap ~648
Search the Microsoft 365 Roadmap for features matching keywords and filters. Combines keyword search, product filtering, status filtering, cloud instance filtering, and recency filtering into a single flexible tool. All filter parameters are optional and can be combined. When no filters are provided, returns the most recent features. Use this tool to: - Browse recent roadmap features (no filters) - Search for features by keyword (query="Copilot") - Filter by product (product="Microsoft Teams") - Find features by status (status="In development", "Rolling out", "Launched") - Filter by cloud instance (cloud_instance="GCC High", "DoD", "GCC") - Retrieve a specific feature by ID (feature_id="534606") - List recently added features (added_within_days=30) - Filter by release phase (release_phase="General Availability", "Preview") - Filter by platform (platform="Web", "iOS", "Android") - Filter by rollout date (rollout_date="2026-03") - Filter by preview date (preview_date="2026-07") - List recently modified features (modified_within_days=7) - Combine any of the above (query="Copilot" + product="Teams" + cloud_instance="GCC")
| Name | Type | Req | Description |
|---|---|---|---|
| added_within_days | – | – | Optional number of days to look back for recently added features (clamped to 1-365). Only features with a created date within this window are returned. |
| cloud_instance | – | – | Optional cloud instance filter (case-insensitive partial match, e.g. "GCC" matches "GCC", "GCC High" matches "GCC High"). |
| feature_id | – | – | Optional roadmap ID to retrieve a single specific feature. When provided, all other filters are ignored. |
| include_facets | boolean | – | When True, includes taxonomy facets (products, statuses, release_rings, platforms, cloud_instances) with occurrence counts in the response. Use with limit=0 to get only facets without features. Facet… |
| limit | integer | – | Maximum number of results to return (default: 10, max: 100). Ignored when feature_id is provided. |
| modified_within_days | – | – | Optional number of days to look back for recently modified features (clamped to 1-365). |
| platform | – | – | Optional platform filter (case-insensitive partial match). |
| preview_date | – | – | Optional preview availability date filter (partial string match against previewAvailabilityDate, e.g. "2026-07"). |
| product | – | – | Optional product tag to filter by (case-insensitive partial match, e.g. "Teams" matches "Microsoft Teams"). |
| query | – | – | Optional keyword to match against title and description (case-insensitive). |
| release_phase | – | – | Optional release phase filter (case-insensitive partial match). |
| rollout_date | – | – | Optional rollout date filter (partial string match against generalAvailabilityDate, e.g. "2026-03"). |
| status | – | – | Optional status filter. Valid values: In development, Rolling out, Launched. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the M365 Roadmap MCP server?
M365 Roadmap is an MCP server listed in the public MCP registry as io.github.jonnybottles/m365-roadmap. Query the Microsoft 365 Roadmap from AI agents. This page covers its PyPI package (m365-roadmap-mcp).
Is the M365 Roadmap MCP server safe to use?
M365 Roadmap scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 M365 Roadmap MCP server expose?
M365 Roadmap exposes 1 tool: search_roadmap. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.
Is the M365 Roadmap MCP server still maintained?
M365 Roadmap 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.