io.github.jonnybottles/azure-updates
PYPI · AZURE-UPDATES-MCP · SCANNED SEP 20
MCP server for Azure Updates RSS feed - search, filter, and summarize Azure service updates
Available components
Recent critical change
CVE-2026-32871 affects this package (3 Aug 2026). See the changelog before you install this server.
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 Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 8 of 77 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 231 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 899 tokens (~299/item across 3 items; 3 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jonnybottles/azure-updates MCP server?
io.github.jonnybottles/azure-updates runs locally as a PyPI package, launched with uvx azure-updates-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 · azure-updates-mcp
claude mcp add jonnybottles-azure-updates -- uvx azure-updates-mcp
{
"mcpServers": {
"jonnybottles-azure-updates": {
"command": "uvx",
"args": [
"azure-updates-mcp"
]
}
}
} {
"servers": {
"jonnybottles-azure-updates": {
"command": "uvx",
"args": [
"azure-updates-mcp"
]
}
}
} codex mcp add jonnybottles-azure-updates -- uvx azure-updates-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jonnybottles-azure-updates": {
"type": "local",
"command": [
"uvx",
"azure-updates-mcp"
],
"enabled": true
}
}
} openclaw mcp add jonnybottles-azure-updates --command uvx --arg azure-updates-mcp
mcp_servers:
jonnybottles-azure-updates:
command: "uvx"
args: ["azure-updates-mcp"] {
"McpServers": {
"jonnybottles-azure-updates": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"azure-updates-mcp"
]
}
}
} assistant mcp add jonnybottles-azure-updates -t stdio -c uvx -a azure-updates-mcp
{
"mcpServers": {
"jonnybottles-azure-updates": {
"command": "uvx",
"args": [
"azure-updates-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 0
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 0
- Stability: pass → 0.80 functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 27 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
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/azure-updates-mcp@0.1.1
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 →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-m8x7-r2rg-vh5g | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-rww4-4w9c-7733 | CVE-2026-27124 | high | yes | |
| GHSA-vv7q-7jx5-f767 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
| PYSEC-2026-2475 | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2476 | CVE-2026-27124 | none | yes | |
| PYSEC-2026-338 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 77 packages
| Packages resolved | 77 |
|---|---|
| Stale | 5 |
| No linked repository | 3 |
| 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 →
azure_updates_list_categories ~94
List all available categories from Azure updates with occurrence counts. Returns every unique category tag found across all updates in the RSS feed, sorted by frequency. Use this to discover valid category values before filtering with azure_updates_search(category=...). Returns: Dictionary with: - total_categories: Number of unique categories - categories: List of objects with 'name' and 'count', sorted by count descending
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
azure_updates_search ~482
Search, filter, and retrieve Azure service updates from the official RSS feed. Combines keyword search, category filtering, status filtering, and date range filtering into a single flexible tool. All filter parameters are optional and can be combined. When no filters are provided, returns the most recent updates. Use this tool to: - Browse recent updates (no filters) - Search for updates mentioning a specific topic (query="AKS") - Filter by service category (category="Azure Kubernetes Service") - Find updates by status (status="In preview", "Launched", "Retirements", "In development") - Get updates in a date range (start_date="2025-01-01", end_date="2025-01-31") - Retrieve a specific update by its GUID (guid="...") - Combine any of the above (query="networking" + status="Launched" + category="AKS") Args: query: Optional keyword to match against title and description (case-insensitive). category: Optional category to filter by (case-insensitive partial match, e.g. "AKS" matches "Azure Kubernetes Service (AKS)"). status: Optional status filter. Valid values: Launched, In preview, In development, Retirements. start_date: Optional start date in ISO format (YYYY-MM-DD). Only include updates published on or after this date. end_date: Optional end date in ISO format (YYYY-MM-DD). Only include updates published on or before this date. Defaults to today when start_date is provided. guid: Optional unique identifier to retrieve a single specific update. When provided, all other filters are ignored and a single update is returned. limit: Maximum number of results to return (default: 10, max: 100). Ignored when guid is provided. Returns: Dictionary with: - total_found: Number of updates matching the filters (before applying limit) - updates: List of matching update objects (up to limit) - filters_applied: Summary of which filters were used
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| end_date | – | – | – |
| guid | – | – | – |
| limit | integer | – | – |
| query | – | – | – |
| start_date | – | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
azure_updates_summarize ~271
Get aggregate statistics and a structured summary of Azure service updates. Provides a dashboard-style overview of Azure updates including counts by status, top categories, date range information, and recent highlights. Optionally scoped to a specific time window. Use this tool to: - Get an overall snapshot of all available updates (no parameters) - Get a summary for the last N weeks (weeks=2 for the past two weeks) - Control how many top categories and highlights are shown (top_n=5) Args: weeks: Optional number of weeks to look back. When omitted, summarizes all available updates. Range: 1-12 when provided. top_n: Number of top categories and highlighted updates to include (default: 10, max: 50). Returns: Dictionary containing: - total_updates: Total number of updates in scope - by_status: Counts for each status type (Launched, In preview, etc.) - top_categories: Top N categories with counts and status breakdowns - date_range: Oldest and newest update dates (and period info if weeks specified) - highlights: Most recent N updates with title, link, status, date, categories
| Name | Type | Req | Description |
|---|---|---|---|
| top_n | integer | – | – |
| weeks | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.jonnybottles/azure-updates MCP server?
io.github.jonnybottles/azure-updates is an MCP server listed in the public MCP registry as io.github.jonnybottles/azure-updates. MCP server for Azure Updates RSS feed - search, filter, and summarize Azure service updates. This page covers its PyPI package (azure-updates-mcp).
What tools does the io.github.jonnybottles/azure-updates MCP server expose?
io.github.jonnybottles/azure-updates exposes 3 tools: azure_updates_search, azure_updates_summarize, azure_updates_list_categories. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.
Is the io.github.jonnybottles/azure-updates MCP server still maintained?
io.github.jonnybottles/azure-updates 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.
What licence is the io.github.jonnybottles/azure-updates MCP server under?
io.github.jonnybottles/azure-updates declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.