Infrawise
NPM · @INFRAWISE/MCP-SERVER · SCANNED SEP 20
Azure FinOps cost optimization for Claude Code: idle resources, rightsizing, reserved savings.
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @azure/msal-node > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 42 of 113 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 65 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 193 tokens (~48/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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 Infrawise MCP server?
Infrawise runs locally as an npm package, launched with npx -y @infrawise/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @infrawise/mcp-server
claude mcp add infrawise-mcp-server -- npx -y @infrawise/mcp-server
{
"mcpServers": {
"infrawise-mcp-server": {
"command": "npx",
"args": [
"-y",
"@infrawise/mcp-server"
]
}
}
} {
"servers": {
"infrawise-mcp-server": {
"command": "npx",
"args": [
"-y",
"@infrawise/mcp-server"
]
}
}
} codex mcp add infrawise-mcp-server -- npx -y @infrawise/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"infrawise-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@infrawise/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add infrawise-mcp-server --command npx --arg -y --arg @infrawise/mcp-server
mcp_servers:
infrawise-mcp-server:
command: "npx"
args: ["-y", "@infrawise/mcp-server"] {
"McpServers": {
"infrawise-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@infrawise/mcp-server"
]
}
}
} assistant mcp add infrawise-mcp-server -t stdio -c npx -a -y @infrawise/mcp-server
{
"mcpServers": {
"infrawise-mcp-server": {
"command": "npx",
"args": [
"-y",
"@infrawise/mcp-server"
]
}
}
} 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 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.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- 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 npm/@infrawise/mcp-server@0.5.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| Deprecated | 1 |
| Stale | 41 |
| 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 →
get_general_recommendations ~44
Retrieve strategic purchasing and licensing optimization recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_filter | string | – | Optional subscription ID to filter results. When omitted, returns merged results across all accessible subscriptions. |
No output schema declared.
No examples provided.
get_idle_resources ~51
Retrieve idle and zombie Azure resources that can be deleted or deallocated for cost savings.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_filter | string | – | Optional subscription ID to filter results. When omitted, returns merged results across all accessible subscriptions. |
No output schema declared.
No examples provided.
get_savings_summary ~50
Aggregate savings totals across idle resources, SKU rightsizing, and general recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_filter | string | – | Optional subscription ID to filter results. When omitted, returns merged results across all accessible subscriptions. |
No output schema declared.
No examples provided.
get_sku_optimizations ~48
Retrieve rightsizing recommendations for overprovisioned resources.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_filter | string | – | Optional subscription ID to filter results. When omitted, returns merged results across all accessible subscriptions. |
No output schema declared.
No examples provided.
What is the Infrawise MCP server?
Infrawise is an MCP server listed in the public MCP registry as io.github.Infrawise/mcp-server. Azure FinOps cost optimization for Claude Code: idle resources, rightsizing, reserved savings. This page covers its npm package (@infrawise/mcp-server).
Is the Infrawise MCP server safe to use?
Infrawise scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 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 Infrawise MCP server expose?
Infrawise exposes 4 tools: get_idle_resources, get_sku_optimizations, get_general_recommendations, get_savings_summary. Their descriptions and schemas cost roughly 193 tokens of context every time the server is loaded.
Is the Infrawise MCP server still maintained?
Infrawise 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 Infrawise MCP server under?
Infrawise declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.