microsoft/mcp is a repository of Microsoft’s Model Context Protocol server implementations, which let AI applications connect to data sources and tools through a shared client-server interface. It supports Microsoft MCP server contributors and the catalogue entries are add-ons for working with these servers.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/microsoft/mcp/azurebackup-telemetry-reportnpx skills add microsoft/mcp --skill azurebackup-telemetry-reportgit clone --depth 1 https://github.com/microsoft/mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/microsoft/mcp/azurebackup-telemetry-report)<a href="https://agentmods.dev/skills/microsoft/mcp/azurebackup-telemetry-report"><img src="https://agentmods.dev/badge/skills/microsoft/mcp/azurebackup-telemetry-report.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00134 | $0.03163 |
| Opus 5 | $0.00067 | $0.01581 |
| Sonnet 5 | $0.00027 | $0.00633 |
| Haiku 4.5 | $0.00013 | $0.00316 |
Grade A, and why
azurebackup-telemetry-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Backup MCP — Weekly Telemetry & Customer Report Generator
Purpose
Generate comprehensive telemetry reports for the Azure Backup MCP toolset by:
- Querying live production telemetry from Kusto
- Classifying errors into Customer / Azure Service / MCP Tool Bug
- Identifying customers via P360/C360 cross-cluster joins (using
P360_CustomerName) - Correlating with merged PRs and releases
- Producing an Outlook-compatible HTML report
When to Use
- Weekly cadence (every Monday or Sunday) to produce the status report
- After a release to assess error rate impact
- When triaging production bugs from telemetry data
- When preparing stakeholder updates on Azure Backup MCP health
- Customer adoption reports for any time range (e.g., last 15 days, 30 days)
- When asked "who is using Azure Backup MCP?" or "generate customer report"
Prerequisites
- Azure authentication configured (the Kusto MCP tool needs access to
ddazureclients.kusto.windows.net) - Access to the
AzureDevExpdatabase on the Kusto cluster - Git access to
microsoft/mcprepository (for PR/release correlation)
Procedure
Step 1: Query Telemetry Data
Run the following KQL queries against the Kusto cluster using the MCP Kusto tool. All queries use:
- Cluster URI:
https://ddazureclients.kusto.windows.net - Database:
AzureDevExp - Function:
getAzureMcpEvents_ToolCalls
1a. Per-Tool Success/Failure with 3-Way Classification (7-day)
This is the primary query. It classifies every call into one of four categories:
- Success: Tool call completed without error
- Customer (4xx): User error — wrong permissions (403), bad input (400), resource not found (404)
- Azure Service: Azure SDK/API/auth layer failed — not an MCP code bug (includes
AggregateException,RequestFailedExceptionwith 5xx) - MCP Tool Bug: Our tool code is wrong —
FormatException,ArgumentNullException,ArgumentException, etc.
Refer to kql-queries.md for the full query.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 222 lines · 134 tokens per session scan A 5ccb5db2f7eb
azurebackup-telemetry-report is a skill published in the GitHub repository microsoft/mcp (3,643 stars, last pushed today), licensed MIT. It adds 134 tokens to every session and 3,163 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…