Utility Matrix
REMOTE · UTILITY-MATRIX.COM
Free browser-based calculators and analyzers for cloud cost, DevOps, security, and data governance.
Available components
Last scanned (22 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category CI/CD and DevOps
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3574 tokens (~115/item across 31 items; 31 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 Management97
- Stability observed for 29 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 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 31 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
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.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://utility-matrix.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=utility-matrix.com | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e989f4128c98927f0ee634a38d2965a0 |
| SANs: utility-matrix.com, *.utility-matrix.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of utility-matrix.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| utility-matrix.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://utility-matrix.com/mcp | Verified | 200 | |
| http (plaintext) | http://utility-matrix.com/mcp | HTTPS enforced | 301 | https://utility-matrix.com/mcp |
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 →
alert-fatigue-calculator Alert Fatigue Calculator ~121
Use when a user asks about alert noise, alert fatigue, or on-call burden from non-actionable alerts. Given weekly alert volume, actionable %, engineer count, and avg resolution time, returns noise rate, wasted hours, and fatigue tier.
| Name | Type | Req | Description |
|---|---|---|---|
| actionable_pct | number | yes | actionable expressed as a percentage. |
| alerts_per_week | number | yes | alerts per week used by this deterministic tool. |
| avg_resolution_min | number | yes | avg resolution min used by this deterministic tool. |
| engineer_count | number | yes | engineer count used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| annual_wasted_hours | number | yes | – |
| burden_per_engineer_hours | number | yes | – |
| computation_basis | string | yes | – |
| fatigue_index | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| noise_alerts_per_week | number | yes | – |
| noise_rate_pct | number | yes | – |
| output_tier | string | yes | – |
| remaining_pct | number | yes | – |
| signal_value | number | yes | – |
| wasted_hours_per_week | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
apdex-score-calculator Apdex Score Calculator ~137
Use this when a user asks about their Apdex score or wants to measure user satisfaction with response times. Takes satisfied, tolerating, and total request counts; satisfied plus tolerating may not exceed total. Returns the Apdex score (0–1) and its rating on the published five-band scale: excellent, good, fair, poor or unacceptable.
| Name | Type | Req | Description |
|---|---|---|---|
| satisfied | number | yes | Requests answered within the target threshold T. |
| tolerating | number | yes | Requests answered between T and 4T. |
| total | number | yes | All requests in the sample, including frustrated ones (slower than 4T or failed). |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| apdex_score | number | yes | – |
| computation_basis | string | yes | – |
| frustrated_pct | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| rating | string | yes | – |
| rating_band | string | yes | – |
| satisfied_pct | number | yes | – |
| tolerating_pct | number | yes | – |
| total_samples | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
availability-sla-calculator Availability SLA Downtime Calculator ~81
Use this when a user asks what a specific availability percentage (like 99.9% or 99.99%) means in downtime minutes per month or year. Converts availability SLA percentage to exact downtime budgets: annual, monthly, weekly, and daily.
| Name | Type | Req | Description |
|---|---|---|---|
| availability_pct | number | yes | e.g. 99.9 for three nines |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| annual_downtime_minutes | number | yes | – |
| availability_tier | string | yes | – |
| computation_basis | string | yes | – |
| interpretation | string | yes | – |
| monthly_downtime_minutes | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| weekly_downtime_minutes | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
canonical-url-auditor Canonical URL Auditor ~67
Audit a page URL against its canonical tag. Detects missing canonical, self-referencing canonical, and relative URL issues.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical | string | yes | The canonical URL found in the page (empty string if missing) |
| page_url | string | yes | The page URL being audited |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| canonical_found | string | – | – |
| computation_basis | string | yes | – |
| interpretation | string | yes | – |
| issue | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| page_url | string | yes | – |
| recommendation | string | yes | – |
| severity | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
certificate-expiry-checker Certificate Expiry Checker ~76
Assess certificate expiry risk given a domain and days remaining. Returns risk level (OK, WARNING at <30 days, CRITICAL at <7 days, EXPIRED at <0).
| Name | Type | Req | Description |
|---|---|---|---|
| days_remaining | number | yes | Days until certificate expires |
| domain | string | yes | Domain name (e.g. "api.example.com") |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| days_remaining | number | yes | – |
| domain | string | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| risk_level | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
change-failure-rate-calculator Change Failure Rate Calculator ~77
Use when a user asks about change failure rate or DORA CFR. Given total and failed deployments, returns failure rate percentage and DORA tier.
| Name | Type | Req | Description |
|---|---|---|---|
| failed_deploys | number | yes | failed deploys used by this deterministic tool. |
| total_deploys | number | yes | total deploys used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| change_failure_rate_pct | number | yes | – |
| computation_basis | string | yes | – |
| dora_rating | string | yes | – |
| failed_count | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| remaining_pct | number | yes | – |
| signal_value | number | yes | – |
| total_count | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
cloud-waste-calculator Cloud Waste Calculator ~108
Use when a user asks about cloud waste, idle resources, or unattached storage. Given monthly cloud bill and idle/oversized percentages, returns waste estimate and tier.
| Name | Type | Req | Description |
|---|---|---|---|
| idle_pct | number | – | idle expressed as a percentage. |
| monthly_cloud_bill | number | yes | monthly cloud bill used by this deterministic tool. |
| oversized_pct | number | – | oversized expressed as a percentage. |
| unattached_volumes_count | number | – | unattached volumes count used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| annualized | number | yes | – |
| computation_basis | string | yes | – |
| do_savings | number | yes | – |
| idle_waste | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| oversized_waste | number | yes | – |
| signal_value | number | yes | – |
| unattached_cost | number | yes | – |
| waste_pct | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
cluster-capacity-calculator Kubernetes Cluster Capacity Calculator ~126
Use this when a user asks for Kubernetes cluster capacity. Uses the same node vCPU, node memory, node count, system reserve, and target utilization model as the browser calculator.
| Name | Type | Req | Description |
|---|---|---|---|
| node_count | number | yes | node count used by this deterministic tool. |
| node_mem_gb | number | yes | node mem in gigabytes. |
| node_vcpu | number | yes | node vcpu used by this deterministic tool. |
| system_reserve_pct | number | – | system reserve expressed as a percentage. |
| target_utilization_pct | number | – | target utilization expressed as a percentage. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| allocatable_factor | number | yes | – |
| computation_basis | string | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| node_count | number | yes | – |
| output_tier | string | yes | – |
| raw_memory_gb | number | yes | – |
| raw_vcpu | number | yes | – |
| remaining_pct | number | yes | – |
| signal_value | number | yes | – |
| usable_memory_gb | number | yes | – |
| usable_vcpu | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
connection-pool-calculator Database Connection Pool Calculator ~131
Use this when a user asks how many database connections to configure. Uses the same max_connections, app server count, database cores, average query duration, and peak RPS model as the browser calculator.
| Name | Type | Req | Description |
|---|---|---|---|
| app_servers | number | yes | app servers used by this deterministic tool. |
| avg_query_ms | number | yes | avg query ms used by this deterministic tool. |
| db_cores | number | yes | db cores used by this deterministic tool. |
| max_connections | number | yes | max connections used by this deterministic tool. |
| peak_rps | number | yes | peak rps used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| estimated_connection_memory_mb | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| peak_concurrent_demand | number | yes | – |
| per_app_pool_size | number | yes | – |
| recommended_pool_total | number | yes | – |
| saturation_pct | number | yes | – |
| status | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
deployment-frequency-calculator Deployment Frequency Calculator ~73
Use when a user asks about deployment frequency or DORA deploy cadence.
| Name | Type | Req | Description |
|---|---|---|---|
| deploys_per_month | number | yes | deploys per month used by this deterministic tool. |
| team_size | number | yes | team size used by this deterministic tool. |
| working_days | number | – | working days used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| deploys_per_day | number | yes | – |
| deploys_per_dev_per_day | number | yes | – |
| deploys_per_week | number | yes | – |
| dora_rating | string | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| remaining_pct | number | yes | – |
| signal_value | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
detect-secrets-scanner Secrets Scanner ~102
Scan text (config, code, env files) for leaked API keys, tokens, passwords, and private keys, plus static code-risk findings such as dynamic code execution, wildcard CORS, unsafe HTML sinks, process spawning and removed security guards. Returns findings with redacted matches and severity classification.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Config, code, or env file content to scan. Do not submit live production secrets; rotate any real credential that appears here. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| code_risk_count | number | yes | – |
| code_risk_findings | array | yes | – |
| computation_basis | string | yes | – |
| finding_count | number | yes | – |
| findings | array | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| severity | string | yes | – |
| types_found | array | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
dockerfile-linter Dockerfile Linter ~118
Lint a Dockerfile against a rule-based subset of Hadolint checks: untagged or :latest base images, interactive or unpinned apt-get installs, apt list cleanup, apk cache, ADD for local files, shell-form CMD/ENTRYPOINT, running as root and a missing HEALTHCHECK. Lines joined with a trailing backslash count as one instruction, and each issue reports its line in the original file.
| Name | Type | Req | Description |
|---|---|---|---|
| dockerfile | string | yes | Dockerfile content (full or partial), up to 8,192 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| error_count | number | yes | – |
| info_count | number | yes | – |
| instruction_count | number | yes | – |
| interpretation | string | yes | – |
| issue_count | number | yes | – |
| issues | array | yes | – |
| line_count | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| severity | string | yes | – |
| warning_count | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
dora-metrics-calculator DORA Metrics Calculator ~176
Use this when a user wants to benchmark an engineering team against DORA metrics. Takes deploys per month, lead time in hours, change failure rate in percent and, optionally, time to restore in hours. Classifies each metric as elite, high, medium or low against fixed benchmark bands; an omitted restore time is reported as unknown and the overall profile is marked partial rather than assumed.
| Name | Type | Req | Description |
|---|---|---|---|
| change_failure_pct | number | yes | Share of deployments that cause a failure in production, in percent. |
| deploys_per_month | number | yes | Production deployments per month. |
| lead_time_hours | number | yes | Lead time for changes, commit to production, in hours. |
| restore_time_hours | number | – | Time to restore service after a failed change, in hours. Optional; when omitted the metric is reported as unknown. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| assessment | string | yes | – |
| change_failure_rate_tier | string | yes | – |
| computation_basis | string | yes | – |
| deploy_frequency_tier | string | yes | – |
| interpretation | string | yes | – |
| lead_time_tier | string | yes | – |
| metrics_assessed | number | yes | – |
| mttr_tier | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| overall_tier | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
ec2-cost-calculator EC2 Cost Calculator ~82
Use when a user asks about EC2 cost. Given instance type and hours, returns monthly cost and DO-equivalent savings estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| hours_per_month | number | – | hours per month used by this deterministic tool. |
| instance_type | string | yes | instance type used by this deterministic tool. |
| os | string | – | os used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| annual_cost | number | yes | – |
| computation_basis | string | yes | – |
| do_equivalent_monthly | number | yes | – |
| do_savings | number | yes | – |
| hourly_rate | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| signal_value | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
egress-cost-calculator Cloud Egress Cost Calculator ~112
Use this when a user asks about monthly internet egress cost from daily request volume, average response size, provider, and CDN offload. Uses the same model as the browser calculator.
| Name | Type | Req | Description |
|---|---|---|---|
| avg_response_kb | number | yes | avg response kb used by this deterministic tool. |
| cdn_pct | number | – | cdn expressed as a percentage. |
| daily_requests | number | yes | daily requests used by this deterministic tool. |
| provider | string | – | Cloud provider whose published pricing model should be applied. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| billable_egress_gb | number | yes | – |
| cdn_offload_gb | number | yes | – |
| cdn_pct | number | yes | – |
| computation_basis | string | yes | – |
| cost_risk | string | yes | – |
| daily_egress_gb | number | yes | – |
| free_tier_gb | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost_usd | number | yes | – |
| monthly_egress_gb | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| origin_egress_gb | number | yes | – |
| provider | string | yes | – |
| rate_per_gb | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
error-budget-calculator SLO Error Budget Calculator ~119
Use this when a user asks about their SLO error budget, remaining error budget, or burn rate. Given SLO percentage and window, returns budget minutes remaining, burn rate multiplier, and status (Under budget / Elevated / ALERTING).
| Name | Type | Req | Description |
|---|---|---|---|
| consumed_minutes | number | – | consumed in minutes. |
| slo_pct | number | yes | Service-level objective target expressed as a percentage. |
| window_days | number | – | Length of the service-level objective window in days. |
| window_elapsed_days | number | – | window elapsed days used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| budget_minutes | number | yes | – |
| burn_rate | number | yes | – |
| computation_basis | string | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| remaining_minutes | number | yes | – |
| status | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
incident-cost-calculator Incident Cost Calculator ~135
Use this when a user asks what an outage or incident cost, or wants to calculate the financial impact of downtime. Takes hourly revenue, downtime duration, and affected percentage. Returns revenue impact, engineering cost, and total incident cost in dollars.
| Name | Type | Req | Description |
|---|---|---|---|
| affected_pct | number | – | affected expressed as a percentage. |
| downtime_hours | number | yes | downtime in hours. |
| eng_hourly | number | – | eng hourly used by this deterministic tool. |
| hourly_revenue | number | yes | hourly revenue used by the calculation; monetary values are in USD unless stated otherwise. |
| responders | number | – | responders used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| engineering_cost_usd | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| revenue_impact_usd | number | yes | – |
| severity | string | yes | – |
| total_cost_usd | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
known-vulnerability-checker Known Vulnerability Checker ~95
Historical curated package-name advisory reference only. Matches older CVE examples for common packages; does not query live feeds or evaluate installed version ranges, so it never proves a package is currently vulnerable or safe.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Package identifier, optionally with a version (e.g. lodash@4.17.21, log4j-core, @babel/core). Versions are not assessed by this historical lookup. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| checked_against | string | yes | – |
| computation_basis | string | yes | – |
| cve | string | – | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| package_name | string | yes | – |
| severity | string | yes | – |
| status | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
kubernetes-manifest-linter Kubernetes Manifest Linter ~59
Lint a Kubernetes manifest (YAML) for common issues: missing resource limits, missing health checks, :latest tag usage, privileged containers. Returns issue list and severity.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | string | yes | Kubernetes manifest YAML content |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| interpretation | string | yes | – |
| issue_count | number | yes | – |
| issues | array | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| severity | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
mttr-calculator MTTR Calculator ~61
Use when a user asks about MTTR or DORA recovery time. Takes incident timestamps (string lines "start,detected,resolved" or array of {start,detected,resolved}).
| Name | Type | Req | Description |
|---|---|---|---|
| incidents | – | yes | incidents used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| dora_rating | string | yes | – |
| incident_count | number | yes | – |
| interpretation | string | yes | – |
| mean_total_minutes | number | yes | – |
| mttd_minutes | number | yes | – |
| mttr_minutes | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| remaining_pct | number | yes | – |
| signal_value | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
on-call-burden-calculator On-Call Burden Calculator ~97
Use when a user asks about on-call load or burnout risk. Uses team size, rotation length, and hourly rate exactly as the browser calculator does.
| Name | Type | Req | Description |
|---|---|---|---|
| hourly_rate | number | yes | hourly rate used by the calculation; monetary values are in USD unless stated otherwise. |
| rotation_weeks | number | yes | rotation weeks used by this deterministic tool. |
| team_size | number | yes | team size used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| annual_cost | number | yes | – |
| computation_basis | string | yes | – |
| hours_per_engineer | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| pct_working_time | number | yes | – |
| remaining_pct | number | yes | – |
| shifts_per_engineer | number | yes | – |
| signal_value | number | yes | – |
| total_hours_per_month | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
pipeline-cost-calculator CI/CD Pipeline Cost Calculator ~198
Use this when a user asks how much their GitHub Actions CI/CD pipeline costs per month. Takes average job duration in minutes, jobs per run, runs per month and the runner label (ubuntu-latest, windows-latest, macos-latest or self-hosted; matched case-insensitively). Uses GitHub list prices for standard hosted runners effective 1 Jan 2026 and GitHub Free's 2,000 included minutes for private repositories, drawn at list price. Self-hosted minutes carry no GitHub charge.
| Name | Type | Req | Description |
|---|---|---|---|
| avg_job_min | number | yes | Average job duration in minutes. |
| jobs_per_run | number | yes | Jobs per workflow run. |
| runner | string | – | Runner label, for example ubuntu-latest, windows-latest, macos-latest or self-hosted. Matched case-insensitively; defaults to Linux. |
| runs_per_month | number | yes | Workflow runs per month. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| billable_minutes | number | yes | – |
| computation_basis | string | yes | – |
| included_minutes | number | yes | – |
| included_minutes_used | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost_usd | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| rate_per_minute_usd | number | yes | – |
| rates_as_of | string | yes | – |
| runner_multiplier | number | yes | – |
| runner_type | string | yes | – |
| severity | string | yes | – |
| total_minutes_per_month | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
precision-recall-f1-calculator Precision, Recall and F1 Calculator ~110
Use this when a user asks about their ML model precision, recall, F1 score, or F-beta score. Takes precision and recall as fractions from 0 to 1 and an optional beta weight. Returns F1, F-beta, and interpretation of the precision-recall tradeoff.
| Name | Type | Req | Description |
|---|---|---|---|
| beta | number | – | beta used by this deterministic tool. |
| precision | number | yes | precision used by this deterministic tool. |
| recall | number | yes | recall used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| beta | number | yes | – |
| computation_basis | string | yes | – |
| f1_score | number | yes | – |
| f_beta_score | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| precision_recall_balance | string | yes | – |
| precision_recall_gap | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
query-cost-estimator PostgreSQL Query Cost Estimator ~115
Estimate PostgreSQL sequential-scan and index-scan cost from table rows, table pages, selectivity, and storage type. Uses the same four-input model as the browser calculator.
| Name | Type | Req | Description |
|---|---|---|---|
| selectivity_pct | number | yes | selectivity expressed as a percentage. |
| storage_type | string | yes | storage type; accepted values: ssd, nvme, hdd, network. |
| table_pages | number | yes | table pages used by this deterministic tool. |
| table_rows | number | yes | table rows used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| cost_ratio | number | yes | – |
| index_pages | number | yes | – |
| index_scan_cost | number | yes | – |
| index_tuples | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| random_page_cost | number | yes | – |
| recommended_plan | string | yes | – |
| sequential_scan_cost | number | yes | – |
| storage_type | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
rate-limit-utilization-calculator API Rate Limit Utilization Calculator ~102
Calculate API rate limit utilization given current request count and limit. Returns utilization percentage, buffer, safety status, and risk level (OK at <80%, WARNING at 80-95%, CRITICAL at >95%).
| Name | Type | Req | Description |
|---|---|---|---|
| current_requests | number | yes | Current request count in the window |
| limit | number | yes | Rate limit ceiling |
| window_seconds | number | – | Rate limit window in seconds (e.g. 60 for per-minute) |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| buffer | number | yes | – |
| computation_basis | string | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| safe | boolean | yes | – |
| status | string | yes | – |
| utilization_pct | number | yes | – |
| why_follow_up | string | yes | – |
| window_seconds | number | yes | – |
No examples provided.
reserved-instance-breakeven Reserved Instance Breakeven Calculator ~245
Use this when a user asks whether to buy Reserved Instances or stay on On-Demand, or how long an RI takes to pay for itself. Takes On-Demand and RI monthly costs plus optional upfront fees (0 when omitted). Judges the 1-year and 3-year terms separately and returns each break-even month and net saving. It recommends a term only when that term saves money over its own length, and prefers 3 years only when it beats three 1-year terms over 36 months at current prices.
| Name | Type | Req | Description |
|---|---|---|---|
| od_monthly | number | yes | On-Demand cost per month in USD. |
| ri_1yr_monthly | number | yes | 1-year Reserved Instance cost per month in USD, excluding the upfront fee. |
| ri_1yr_upfront | number | – | 1-year upfront fee in USD; 0 when omitted (no-upfront RI). |
| ri_3yr_monthly | number | yes | 3-year Reserved Instance cost per month in USD, excluding the upfront fee. |
| ri_3yr_upfront | number | – | 3-year upfront fee in USD; 0 when omitted (no-upfront RI). |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| breakeven_months | number | – | – |
| breakeven_months_3yr | number | – | – |
| computation_basis | string | yes | – |
| interpretation | string | yes | – |
| monthly_saving_1yr_usd | number | yes | – |
| monthly_saving_3yr_usd | number | yes | – |
| net_savings_1yr_usd | number | yes | – |
| net_savings_3yr_usd | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| recommended_term | string | yes | – |
| severity | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
rightsizing-calculator Compute Rightsizing Calculator ~130
Use when a user asks about instance rightsizing or overprovisioned compute.
| Name | Type | Req | Description |
|---|---|---|---|
| current_memory_gb | number | yes | current memory in gigabytes. |
| current_vcpu | number | yes | current vcpu used by this deterministic tool. |
| hourly_cost | number | – | hourly cost used by the calculation; monetary values are in USD unless stated otherwise. |
| instance_count | number | – | instance count used by this deterministic tool. |
| p99_cpu_pct | number | yes | p99 cpu expressed as a percentage. |
| p99_memory_pct | number | yes | p99 memory expressed as a percentage. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| annual_savings | number | yes | – |
| computation_basis | string | yes | – |
| do_savings | number | yes | – |
| instance_count | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost | number | yes | – |
| needed_memory_gb | number | yes | – |
| needed_vcpu | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| savings_factor | number | yes | – |
| signal_value | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
slo-burn-rate-calculator SLO Burn Rate Calculator ~127
Use this when a user asks how fast they are burning their error budget, or whether their current error rate will exhaust their SLO window. Takes error count, total requests, SLO target, and observation window. Returns burn rate and budget consumption per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| errors | number | yes | Number of failed requests observed in the measurement window. |
| slo | number | yes | Service-level objective target expressed as a percentage. |
| total | number | yes | Total number of requests observed in the measurement window. |
| window_hours | number | yes | Length of the observed measurement window in hours. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| budget_consumed_pct_per_hour | number | yes | – |
| burn_rate | number | yes | – |
| computation_basis | string | yes | – |
| error_rate_pct | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| status | string | yes | – |
| why_follow_up | string | yes | – |
| window_hours | number | yes | – |
No examples provided.
software-purchase-risk-calculator Software Purchase Risk Calculator ~158
Use when a user asks about risk of a software purchase or SaaS commitment.
| Name | Type | Req | Description |
|---|---|---|---|
| changeManagementRisk | number | – | changeManagementRisk used by this deterministic tool. |
| contractLengthMonths | number | – | contractLengthMonths used by this deterministic tool. |
| integrationCount | number | – | integrationCount used by this deterministic tool. |
| internalHourlyCost | number | – | internalHourlyCost used by this deterministic tool. |
| monthlySubscription | number | yes | monthlySubscription used by this deterministic tool. |
| numUsers | number | – | numUsers used by this deterministic tool. |
| setupHours | number | – | setupHours used by this deterministic tool. |
| vendorStabilityScore | number | – | vendorStabilityScore used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_component | number | yes | – |
| affiliate_context | object | – | – |
| complexity_component | number | yes | – |
| computation_basis | string | yes | – |
| contract_months | number | yes | – |
| contract_total | number | yes | – |
| integration_component | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| risk_score | number | yes | – |
| signal_value | number | yes | – |
| vendor_component | number | yes | – |
| why_follow_up | string | yes | – |
| year1_labor_cost | number | yes | – |
| year1_sub_cost | number | yes | – |
| year1_total_cost | number | yes | – |
No examples provided.
terraform-plan-cost-estimator Terraform Plan Cost Estimator ~68
Use when a user asks to estimate monthly cost of a Terraform plan.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | count used by this deterministic tool. |
| instance_size | string | – | instance size used by this deterministic tool. |
| resource_type | string | yes | resource type used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| annual_cost | number | yes | – |
| computation_basis | string | yes | – |
| hourly_rate | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| resource_count | number | yes | – |
| resource_type | string | yes | – |
| signal_value | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
total-cost-of-ownership-calculator Total Cost of Ownership Calculator ~168
Use when a user asks about TCO or multi-year SaaS cost.
| Name | Type | Req | Description |
|---|---|---|---|
| adminHoursPerMonth | number | – | adminHoursPerMonth used by this deterministic tool. |
| baseMonthlySubscription | number | – | baseMonthlySubscription used by this deterministic tool. |
| contractLength | number | – | contractLength used by this deterministic tool. |
| expectedActiveUsers | number | yes | expectedActiveUsers used by this deterministic tool. |
| internalHourlyCost105 | number | – | internalHourlyCost105 used by this deterministic tool. |
| numPaidSeats | number | yes | numPaidSeats used by this deterministic tool. |
| oneTimeFees | number | – | oneTimeFees used by this deterministic tool. |
| perUserMonthlyFee | number | – | perUserMonthlyFee used by this deterministic tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| contract_months | number | yes | – |
| contract_total | number | yes | – |
| cost_per_user_monthly | number | yes | – |
| do_savings | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| output_tier | string | yes | – |
| overpaying_flags | number | yes | – |
| seat_waste_cost_yr | number | yes | – |
| seat_waste_pct | number | yes | – |
| shelfware_seats | number | yes | – |
| signal_value | number | yes | – |
| why_follow_up | string | yes | – |
| year1_admin_cost | number | yes | – |
| year1_total_cost | number | yes | – |
| year1_vendor_cost | number | yes | – |
No examples provided.
How do I install the Utility Matrix MCP server?
Utility Matrix is a hosted endpoint at https://utility-matrix.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · utility-matrix.com
claude mcp add --transport http helphub369-utility-matrix 'https://utility-matrix.com/mcp'
What is the Utility Matrix MCP server?
Utility Matrix is an MCP server listed in the public MCP registry as io.github.helphub369/utility-matrix. Free browser-based calculators and analyzers for cloud cost, DevOps, security, and data governance. This page covers its hosted endpoint (https://utility-matrix.com/mcp).
Is the Utility Matrix MCP server safe to use?
Utility Matrix scores 84 out of 100 on VerifyMCP. 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 Utility Matrix MCP server expose?
Utility Matrix exposes 31 tools: error-budget-calculator, slo-burn-rate-calculator, incident-cost-calculator, reserved-instance-breakeven, availability-sla-calculator, and 26 more. Their descriptions and schemas cost roughly 3,574 tokens of context every time the server is loaded.
Does the Utility Matrix MCP server require authentication?
No. We connected to Utility Matrix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Utility Matrix MCP server still maintained?
Utility Matrix is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.