io.github.MrHenrySword/agile-analytics-mcp
NPM · @BAYTEKDEV/AGILE-ANALYTICS-MCP
Azure DevOps sprint, cycle time, flow, WIP, aging and forecast metrics. Local, read-only.
Available components
Last scanned (18 hours ago)
Scores higher than 49% of npm servers
Category Data and Analytics
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency35
- 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2009 tokens (~287/item across 7 items; 7 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
- Security disclosure: fail → pass ▲ functional
- 20 Nov 26 +1
- Package version: 6.79.2 → 6.80.0 functional
- 19 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.30 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 6.79.1 → 6.79.2 functional
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +17
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 158 → 287 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- Schema quality: good → excellent functional
- Package version: 6.78.0 → 6.79.1 functional
- 12 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 6.77.4 → 6.78.0 functional
- 11 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 6.75.3 → 6.77.4 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 21 Nov 2026 · Analysed npm/@baytekdev/agile-analytics-mcp@6.80.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
aging Aging work items ~302
Open work in the current sprint as the Aging view lists it, carried-over items from the previous sprint included: per item its stage, days in that stage and days in flow, in the weekend basis the Aging view uses for this person (weekendBasis says which). Answers with numbers, dates, states and work item ids only; never work item titles, descriptions, comments, tags or assigned people, and never calls Baytek. Uses the customer’s saved workflow mapping only; no mapping answers {"error":"workflow-not-mapped"}. {"error":"licence-inactive"} means the organisation’s trial has ended without a valid licence, or its licence has not been confirmed for 30 days: tell the person to open Agile Analytics in Azure DevOps and, if the answer stays the same, to ask an admin to look at Configuration → License. {"error":"no-seat"} means the plan gives Agile Analytics to assigned people only and this person has no seat: tell them to open Agile Analytics in Azure DevOps once and ask again and, if the answer stays the same, to ask an extension admin for a seat (Configuration → Access Control). {"error":"throttled"} or {"error":"timed-out"}: wait a minute and ask again.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | Azure DevOps organisation name (dev.azure.com/<org>). |
| project | string | yes | Project name or id. |
| team | string | yes | Team name or id. |
Structured output declared, but exposes no named fields.
No examples provided.
cycle_time Cycle time ~312
Cycle time over the last N finished sprints, as the Cycle Time view plots it: count, average, p50/p70/p85/p95 days, per Item Types category, slowest ids. Answers with numbers, dates, states and work item ids only; never work item titles, descriptions, comments, tags or assigned people, and never calls Baytek. Uses the customer’s saved workflow mapping only; no mapping answers {"error":"workflow-not-mapped"}. {"error":"licence-inactive"} means the organisation’s trial has ended without a valid licence, or its licence has not been confirmed for 30 days: tell the person to open Agile Analytics in Azure DevOps and, if the answer stays the same, to ask an admin to look at Configuration → License. {"error":"no-seat"} means the plan gives Agile Analytics to assigned people only and this person has no seat: tell them to open Agile Analytics in Azure DevOps once and ask again and, if the answer stays the same, to ask an extension admin for a seat (Configuration → Access Control). {"error":"throttled"} or {"error":"timed-out"}: wait a minute and ask again.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | Azure DevOps organisation name (dev.azure.com/<org>). |
| project | string | yes | Project name or id. |
| sprints | integer | – | How many finished sprints (default 6). Never the running one. |
| team | string | yes | Team name or id. |
Structured output declared, but exposes no named fields.
No examples provided.
flow_efficiency Flow efficiency ~290
Flow efficiency over the last N finished sprints, as the Flow Efficiency view computes it. Answers with numbers, dates, states and work item ids only; never work item titles, descriptions, comments, tags or assigned people, and never calls Baytek. Uses the customer’s saved workflow mapping only; no mapping answers {"error":"workflow-not-mapped"}. {"error":"licence-inactive"} means the organisation’s trial has ended without a valid licence, or its licence has not been confirmed for 30 days: tell the person to open Agile Analytics in Azure DevOps and, if the answer stays the same, to ask an admin to look at Configuration → License. {"error":"no-seat"} means the plan gives Agile Analytics to assigned people only and this person has no seat: tell them to open Agile Analytics in Azure DevOps once and ask again and, if the answer stays the same, to ask an extension admin for a seat (Configuration → Access Control). {"error":"throttled"} or {"error":"timed-out"}: wait a minute and ask again.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | Azure DevOps organisation name (dev.azure.com/<org>). |
| project | string | yes | Project name or id. |
| sprints | integer | – | How many finished sprints (default 6). Never the running one. |
| team | string | yes | Team name or id. |
Structured output declared, but exposes no named fields.
No examples provided.
forecast Monte Carlo forecast ~364
Monte Carlo forecast from the throughput of the finished sprints among the last 12: how many items in a window, or when a backlog finishes. sampleSprints is how many sprints it drew from: say that number with the forecast. The hub’s Monte Carlo view and Dashboard start from the 6 newest finished sprints, so their figures can differ from this one. Answers with numbers, dates, states and work item ids only; never work item titles, descriptions, comments, tags or assigned people, and never calls Baytek. Uses the customer’s saved workflow mapping only; no mapping answers {"error":"workflow-not-mapped"}. {"error":"licence-inactive"} means the organisation’s trial has ended without a valid licence, or its licence has not been confirmed for 30 days: tell the person to open Agile Analytics in Azure DevOps and, if the answer stays the same, to ask an admin to look at Configuration → License. {"error":"no-seat"} means the plan gives Agile Analytics to assigned people only and this person has no seat: tell them to open Agile Analytics in Azure DevOps once and ask again and, if the answer stays the same, to ask an extension admin for a seat (Configuration → Access Control). {"error":"throttled"} or {"error":"timed-out"}: wait a minute and ask again.
| Name | Type | Req | Description |
|---|---|---|---|
| backlog | integer | – | when: number of items to finish. |
| mode | string | – | – |
| org | string | yes | Azure DevOps organisation name (dev.azure.com/<org>). |
| project | string | yes | Project name or id. |
| team | string | yes | Team name or id. |
| windowDays | integer | – | howMany: forecast horizon in days (default 30). |
Structured output declared, but exposes no named fields.
No examples provided.
sprint_summary Sprint summary ~321
One sprint as the Sprint Summary view counts it: delivered items and points, cycle time, carryover, and commitment (committed at the end of day one, completed of committed, reliability, scope added and removed). Answers with numbers, dates, states and work item ids only; never work item titles, descriptions, comments, tags or assigned people, and never calls Baytek. Uses the customer’s saved workflow mapping only; no mapping answers {"error":"workflow-not-mapped"}. {"error":"licence-inactive"} means the organisation’s trial has ended without a valid licence, or its licence has not been confirmed for 30 days: tell the person to open Agile Analytics in Azure DevOps and, if the answer stays the same, to ask an admin to look at Configuration → License. {"error":"no-seat"} means the plan gives Agile Analytics to assigned people only and this person has no seat: tell them to open Agile Analytics in Azure DevOps once and ask again and, if the answer stays the same, to ask an extension admin for a seat (Configuration → Access Control). {"error":"throttled"} or {"error":"timed-out"}: wait a minute and ask again.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | Azure DevOps organisation name (dev.azure.com/<org>). |
| project | string | yes | Project name or id. |
| sprintId | string | – | Iteration GUID. Default: the last finished sprint (a running sprint is never summarised by default). |
| team | string | yes | Team name or id. |
Structured output declared, but exposes no named fields.
No examples provided.
status Connector status check ~148
Checks what the connector needs before it can answer, in the order every tool checks it, and reports each check as a fixed word: sign-in, extension settings, admin switch, licence, seat, the workflow mapping (only when a project and team are given) and the plan (open = the Premium extras are included). A check after one that failed is not-checked. Call it when a tool answers an error, or to set up. Answers fixed words only and never calls Baytek.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | Azure DevOps organisation name (dev.azure.com/<org>). |
| project | string | – | Project name or id. |
| team | string | – | Team name or id. |
Structured output declared, but exposes no named fields.
No examples provided.
wip Work in progress ~272
Items in progress right now in the running sprint, by workflow stage, with this person’s saved WIP limit. Answers with numbers, dates, states and work item ids only; never work item titles, descriptions, comments, tags or assigned people, and never calls Baytek. Uses the customer’s saved workflow mapping only; no mapping answers {"error":"workflow-not-mapped"}. {"error":"licence-inactive"} means the organisation’s trial has ended without a valid licence, or its licence has not been confirmed for 30 days: tell the person to open Agile Analytics in Azure DevOps and, if the answer stays the same, to ask an admin to look at Configuration → License. {"error":"no-seat"} means the plan gives Agile Analytics to assigned people only and this person has no seat: tell them to open Agile Analytics in Azure DevOps once and ask again and, if the answer stays the same, to ask an extension admin for a seat (Configuration → Access Control). {"error":"throttled"} or {"error":"timed-out"}: wait a minute and ask again.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | yes | Azure DevOps organisation name (dev.azure.com/<org>). |
| project | string | yes | Project name or id. |
| team | string | yes | Team name or id. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.MrHenrySword/agile-analytics-mcp server?
io.github.MrHenrySword/agile-analytics-mcp runs locally as an npm package, launched with npx -y @baytekdev/agile-analytics-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @baytekdev/agile-analytics-mcp
claude mcp add mrhenrysword-agile-analytics-mcp -- npx -y @baytekdev/agile-analytics-mcp
What is the io.github.MrHenrySword/agile-analytics-mcp server?
io.github.MrHenrySword/agile-analytics-mcp is listed in the public MCP registry as io.github.MrHenrySword/agile-analytics-mcp. Azure DevOps sprint, cycle time, flow, WIP, aging and forecast metrics. Local, read-only. This page covers its npm package (@baytekdev/agile-analytics-mcp).
Is the io.github.MrHenrySword/agile-analytics-mcp server safe to use?
io.github.MrHenrySword/agile-analytics-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.MrHenrySword/agile-analytics-mcp server expose?
io.github.MrHenrySword/agile-analytics-mcp exposes 7 tools: sprint_summary, cycle_time, flow_efficiency, wip, aging, and 2 more. Their descriptions and schemas cost roughly 2,009 tokens of context every time the server is loaded.
Is the io.github.MrHenrySword/agile-analytics-mcp server still maintained?
io.github.MrHenrySword/agile-analytics-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.MrHenrySword/agile-analytics-mcp server?
VerifyMCP ran 15 checks on io.github.MrHenrySword/agile-analytics-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.MrHenrySword/agile-analytics-mcp: License. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.