Utility Matrix
REMOTE · UTILITY-MATRIX.COM · SCANNED SEP 20
Free browser-based calculators and analyzers for cloud cost, DevOps, security, and data governance.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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'
{
"mcpServers": {
"helphub369-utility-matrix": {
"url": "https://utility-matrix.com/mcp"
}
}
} {
"servers": {
"helphub369-utility-matrix": {
"type": "http",
"url": "https://utility-matrix.com/mcp"
}
}
} [mcp_servers.helphub369-utility-matrix] url = "https://utility-matrix.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"helphub369-utility-matrix": {
"type": "remote",
"url": "https://utility-matrix.com/mcp",
"enabled": true
}
}
} openclaw mcp add helphub369-utility-matrix --url 'https://utility-matrix.com/mcp' --transport streamable-http
mcp_servers:
helphub369-utility-matrix:
url: "https://utility-matrix.com/mcp" {
"McpServers": {
"helphub369-utility-matrix": {
"Transport": "http",
"Url": "https://utility-matrix.com/mcp"
}
}
} assistant mcp add helphub369-utility-matrix -t streamable-http -u 'https://utility-matrix.com/mcp'
{
"mcpServers": {
"helphub369-utility-matrix": {
"type": "http",
"url": "https://utility-matrix.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.47 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 · 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 | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 73fe50d9cac6657b136e28a9dc9fdf76 |
| 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 | Not MCP | 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 ~93
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 | – |
| alerts_per_week | number | yes | – |
| avg_resolution_min | number | yes | – |
| engineer_count | number | yes | – |
| 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 ~78
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. Returns Apdex score (0–1) and performance rating.
| Name | Type | Req | Description |
|---|---|---|---|
| satisfied | number | yes | – |
| tolerating | number | yes | – |
| total | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| apdex_score | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| rating | string | yes | – |
| satisfied_pct | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
availability-sla-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 | – |
| 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 ~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 | yes | – |
| 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 ~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 ~61
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 | – |
| total_deploys | number | yes | – |
| 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 ~81
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 | – | – |
| monthly_cloud_bill | number | yes | – |
| oversized_pct | number | – | – |
| unattached_volumes_count | number | – | – |
| 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 ~129
Use this when a user asks whether their Kubernetes cluster has enough capacity, or how many more pods they can schedule. Takes node count (`nodes`), CPU cores per node (`node_cpu`), memory per node in GB (`node_memory_gb`), pod count (`pods`), and resource requests. Returns cluster utilization and headroom.
| Name | Type | Req | Description |
|---|---|---|---|
| node_cpu | number | yes | – |
| node_memory_gb | number | yes | – |
| nodes | number | yes | – |
| pod_cpu_m | number | – | – |
| pod_memory_mb | number | – | – |
| pods | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| allocatable_cpu_cores | number | yes | – |
| allocatable_memory_gb | number | yes | – |
| cpu_utilization_pct | number | yes | – |
| interpretation | string | yes | – |
| memory_utilization_pct | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| pressure_level | string | yes | – |
| severity | string | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
connection-pool-calculator ~82
Use this when a user asks how many database connections to configure in their connection pool, or is troubleshooting PostgreSQL connection exhaustion. Takes CPU cores, app instances, and max_connections. Returns recommended pool size per instance with utilization ratio.
| Name | Type | Req | Description |
|---|---|---|---|
| app_instances | number | – | – |
| cpu_cores | number | yes | – |
| max_connections | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| interpretation | string | yes | – |
| max_connections_utilization_pct | – | – | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| per_app_instance | number | yes | – |
| recommended_pool_total | number | yes | – |
| warning | boolean | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
deployment-frequency-calculator ~50
Use when a user asks about deployment frequency or DORA deploy cadence.
| Name | Type | Req | Description |
|---|---|---|---|
| deploys_per_month | number | yes | – |
| team_size | number | yes | – |
| working_days | number | – | – |
| 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 ~63
Scan text (config, code, env files) for leaked API keys, tokens, passwords, and private keys. Returns findings with redacted matches and severity classification.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Config, code, or env file content to scan for secrets |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| 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 ~57
Lint a Dockerfile for common issues: :latest tag on FROM, interactive installs without -y, running as root. Returns issues with suggestions per instruction.
| Name | Type | Req | Description |
|---|---|---|---|
| dockerfile | string | yes | Dockerfile content (full or partial) |
| 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.
dora-metrics-calculator ~103
Use this when a user wants to benchmark their engineering team against DORA metrics, or classify their deployment frequency and lead time. Takes deploy frequency, lead time hours, change failure rate, and restore time. Returns Elite/High/Medium/Low tier classification per metric.
| Name | Type | Req | Description |
|---|---|---|---|
| change_failure_pct | number | yes | – |
| deploys_per_month | number | yes | – |
| lead_time_hours | number | yes | – |
| restore_time_hours | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| change_failure_rate_tier | string | yes | – |
| deploy_frequency_tier | string | yes | – |
| interpretation | string | yes | – |
| lead_time_tier | string | 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 ~61
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 | – | – |
| instance_type | string | yes | – |
| os | string | – | – |
| 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 ~65
Use this when a user asks how much AWS data transfer or egress costs, or wants to estimate their monthly data transfer bill. Takes monthly transfer volume in GB. Returns estimated monthly egress cost using AWS tiered pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| transfer_gb | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| cost_risk | string | yes | – |
| effective_rate_per_gb | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost_usd | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| transfer_gb | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
error-budget-calculator ~91
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 | – | – |
| slo_pct | number | yes | – |
| window_days | number | – | – |
| window_elapsed_days | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| budget_minutes | number | yes | – |
| burn_rate | number | 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 ~99
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 | – | – |
| downtime_hours | number | yes | – |
| eng_hourly | number | – | – |
| hourly_revenue | number | yes | – |
| responders | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| 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 ~81
Check a package name against a database of known CVEs. Returns vulnerability status, CVE ID, and severity for common packages (log4j, lodash, moment, axios, django, flask, pillow, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Package name to check (e.g. "lodash", "log4j", "django") |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| checked_against | string | yes | – |
| computation_basis | string | yes | – |
| cve | string | yes | – |
| 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 ~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 ~55
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 | – |
| 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 ~60
Use when a user asks about on-call load or burnout risk.
| Name | Type | Req | Description |
|---|---|---|---|
| engineer_count | number | yes | – |
| hourly_cost | number | yes | – |
| hours_per_shift | number | yes | – |
| shifts_per_month | number | yes | – |
| 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 ~96
Use this when a user asks how much their GitHub Actions CI/CD pipeline costs per month, or wants to compare runner costs. Takes average job duration, jobs per run, monthly run count, and runner type. Returns monthly billing cost with runner multiplier breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| avg_job_min | number | yes | – |
| jobs_per_run | number | yes | – |
| runner | string | – | – |
| runs_per_month | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| billable_minutes | number | yes | – |
| interpretation | string | yes | – |
| monthly_cost_usd | number | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| runner_multiplier | number | yes | – |
| severity | string | yes | – |
| total_minutes_per_month | number | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
precision-recall-f1-calculator ~84
Use this when a user asks about their ML model precision, recall, F1 score, or F-beta score. Takes precision, recall, and optional beta weight. Returns F1, F-beta, and interpretation of the precision-recall tradeoff.
| Name | Type | Req | Description |
|---|---|---|---|
| beta | number | – | – |
| precision | number | yes | – |
| recall | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| 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 | – |
| why_follow_up | string | yes | – |
No examples provided.
query-cost-estimator ~58
Estimate the relative cost of a SQL query based on heuristic analysis: SELECT *, JOIN count, missing WHERE/LIMIT, leading wildcards, unbounded sorts. Returns cost score and level.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | SQL query to analyze |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| computation_basis | string | yes | – |
| cost_level | string | yes | – |
| cost_score | number | yes | – |
| interpretation | string | yes | – |
| next_step | string | yes | – |
| next_step_url | string | yes | – |
| warning_count | number | yes | – |
| warnings | array | yes | – |
| why_follow_up | string | yes | – |
No examples provided.
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 ~126
Use this when a user asks whether to buy Reserved Instances or stay on On-Demand, or how long until an RI pays for itself. Takes On-Demand and RI monthly costs plus upfront fee. Returns break-even month and net savings over 1yr and 3yr terms.
| Name | Type | Req | Description |
|---|---|---|---|
| od_monthly | number | yes | – |
| ri_1yr_monthly | number | yes | – |
| ri_1yr_upfront | number | – | – |
| ri_3yr_monthly | number | yes | – |
| ri_3yr_upfront | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| breakeven_months | number | yes | – |
| interpretation | string | 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 ~81
Use when a user asks about instance rightsizing or overprovisioned compute.
| Name | Type | Req | Description |
|---|---|---|---|
| current_memory_gb | number | yes | – |
| current_vcpu | number | yes | – |
| hourly_cost | number | – | – |
| instance_count | number | – | – |
| p99_cpu_pct | number | yes | – |
| p99_memory_pct | number | yes | – |
| 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 ~83
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 and total requests over a period, returns burn rate multiple and time-to-exhaustion signal.
| Name | Type | Req | Description |
|---|---|---|---|
| errors | number | yes | – |
| slo | number | yes | – |
| total | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_context | object | – | – |
| budget_consumed_pct_per_hour | number | yes | – |
| burn_rate | number | 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 | – |
No examples provided.
software-purchase-risk-calculator ~97
Use when a user asks about risk of a software purchase or SaaS commitment.
| Name | Type | Req | Description |
|---|---|---|---|
| changeManagementRisk | number | – | – |
| contractLengthMonths | number | – | – |
| integrationCount | number | – | – |
| internalHourlyCost | number | – | – |
| monthlySubscription | number | yes | – |
| numUsers | number | – | – |
| setupHours | number | – | – |
| vendorStabilityScore | number | – | – |
| 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 ~48
Use when a user asks to estimate monthly cost of a Terraform plan.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| instance_size | string | – | – |
| resource_type | string | yes | – |
| 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 ~102
Use when a user asks about TCO or multi-year SaaS cost.
| Name | Type | Req | Description |
|---|---|---|---|
| adminHoursPerMonth | number | – | – |
| baseMonthlySubscription | number | – | – |
| contractLength | number | – | – |
| expectedActiveUsers | number | yes | – |
| internalHourlyCost105 | number | – | – |
| numPaidSeats | number | yes | – |
| oneTimeFees | number | – | – |
| perUserMonthlyFee | number | – | – |
| 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.
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 23 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 2,469 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.