Server providing Argo CD integration for MCP clients.
Nothing to run from here
Utility Matrix is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
31
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Free browser-based calculators and analyzers for cloud cost, DevOps, security, and data governance.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http utility-matrix-mcp https://utility-matrix.com/mcp
# 2 — ask your agent for something these tools do
# error-budget-calculator, slo-burn-rate-calculator, incident-cost-calculator and 28 more
Utility Matrix costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HEAll 3 servers
helphub3693 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http utility-matrix-mcp https://utility-matrix.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
31 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slo_pct | number | yes | Service-level objective target expressed as a percentage. |
| window_days | number | no | Length of the service-level objective window in days. |
| consumed_minutes | number | no | consumed in minutes. |
| window_elapsed_days | number | no | window elapsed days used by this deterministic tool. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| errors | number | yes | Number of failed requests observed in the measurement window. |
| total | number | yes | Total number of requests observed in the measurement window. |
| slo | number | yes | Service-level objective target expressed as a percentage. |
| window_hours | number | yes | Length of the observed measurement window in hours. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hourly_revenue | number | yes | hourly revenue used by the calculation; monetary values are in USD unless stated otherwise. |
| downtime_hours | number | yes | downtime in hours. |
| affected_pct | number | no | affected expressed as a percentage. |
| responders | number | no | responders used by this deterministic tool. |
| eng_hourly | number | no | eng hourly used by this deterministic tool. |
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 onl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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_3yr_monthly | number | yes | 3-year Reserved Instance cost per month in USD, excluding the upfront fee. |
| ri_1yr_upfront | number | no | 1-year upfront fee in USD; 0 when omitted (no-upfront RI). |
| ri_3yr_upfront | number | no | 3-year upfront fee in USD; 0 when omitted (no-upfront RI). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| availability_pct | number | yes | e.g. 99.9 for three nines |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deploys_per_month | number | yes | Production deployments per month. |
| lead_time_hours | number | yes | Lead time for changes, commit to production, in hours. |
| change_failure_pct | number | yes | Share of deployments that cause a failure in production, in percent. |
| restore_time_hours | number | no | Time to restore service after a failed change, in hours. Optional; when omitted the metric is reported as unknown. |
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 reposit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| avg_job_min | number | yes | Average job duration in minutes. |
| jobs_per_run | number | yes | Jobs per workflow run. |
| runs_per_month | number | yes | Workflow runs per month. |
| runner | string | no | Runner label, for example ubuntu-latest, windows-latest, macos-latest or self-hosted. Matched case-insensitively; defaults to Linux. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_connections | number | yes | max connections used by this deterministic tool. |
| app_servers | number | yes | app servers used by this deterministic tool. |
| db_cores | number | yes | db cores used by this deterministic tool. |
| avg_query_ms | number | yes | avg query ms used by this deterministic tool. |
| peak_rps | number | yes | peak rps used by this deterministic tool. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node_vcpu | number | yes | node vcpu used by this deterministic tool. |
| node_mem_gb | number | yes | node mem in gigabytes. |
| node_count | number | yes | node count used by this deterministic tool. |
| system_reserve_pct | number | no | system reserve expressed as a percentage. |
| target_utilization_pct | number | no | target utilization expressed as a percentage. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| precision | number | yes | precision used by this deterministic tool. |
| recall | number | yes | recall used by this deterministic tool. |
| beta | number | no | beta used by this deterministic tool. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| daily_requests | number | yes | daily requests used by this deterministic tool. |
| avg_response_kb | number | yes | avg response kb used by this deterministic tool. |
| provider | string | no | Cloud provider whose published pricing model should be applied. |
| cdn_pct | number | no | cdn expressed as a percentage. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Config, code, or env file content to scan. Do not submit live production secrets; rotate any real credential that appears here. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain name (e.g. "api.example.com") |
| days_remaining | number | yes | Days until certificate expires |
Lint a Kubernetes manifest (YAML) for common issues: missing resource limits, missing health checks, :latest tag usage, privileged containers. Returns issue list and severity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manifest | string | yes | Kubernetes manifest YAML content |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dockerfile | string | yes | Dockerfile content (full or partial), up to 8,192 characters. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| table_rows | number | yes | table rows used by this deterministic tool. |
| table_pages | number | yes | table pages used by this deterministic tool. |
| selectivity_pct | number | yes | selectivity expressed as a percentage. |
| storage_type | string | yes | storage type; accepted values: ssd, nvme, hdd, network. |
Audit a page URL against its canonical tag. Detects missing canonical, self-referencing canonical, and relative URL issues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_url | string | yes | The page URL being audited |
| canonical | string | yes | The canonical URL found in the page (empty string if missing) |
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%).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| current_requests | number | yes | Current request count in the window |
| limit | number | yes | Rate limit ceiling |
| window_seconds | number | no | Rate limit window in seconds (e.g. 60 for per-minute) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alerts_per_week | number | yes | alerts per week used by this deterministic tool. |
| actionable_pct | number | yes | actionable expressed as a percentage. |
| engineer_count | number | yes | engineer count used by this deterministic tool. |
| avg_resolution_min | number | yes | avg resolution min used by this deterministic tool. |
Use when a user asks about change failure rate or DORA CFR. Given total and failed deployments, returns failure rate percentage and DORA tier.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| total_deploys | number | yes | total deploys used by this deterministic tool. |
| failed_deploys | number | yes | failed deploys used by this deterministic tool. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monthly_cloud_bill | number | yes | monthly cloud bill used by this deterministic tool. |
| idle_pct | number | no | idle expressed as a percentage. |
| oversized_pct | number | no | oversized expressed as a percentage. |
| unattached_volumes_count | number | no | unattached volumes count used by this deterministic tool. |
Use when a user asks about deployment frequency or DORA deploy cadence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | working days used by this deterministic tool. |
Use when a user asks about EC2 cost. Given instance type and hours, returns monthly cost and DO-equivalent savings estimate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance_type | string | yes | instance type used by this deterministic tool. |
| hours_per_month | number | no | hours per month used by this deterministic tool. |
| os | string | no | os used by this deterministic tool. |
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}).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| incidents | yes | incidents used by this deterministic tool. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_size | number | yes | team size used by this deterministic tool. |
| rotation_weeks | number | yes | rotation weeks used by this deterministic tool. |
| hourly_rate | number | yes | hourly rate used by the calculation; monetary values are in USD unless stated otherwise. |
Use when a user asks about instance rightsizing or overprovisioned compute.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| current_vcpu | number | yes | current vcpu used by this deterministic tool. |
| p99_cpu_pct | number | yes | p99 cpu expressed as a percentage. |
| current_memory_gb | number | yes | current memory in gigabytes. |
| p99_memory_pct | number | yes | p99 memory expressed as a percentage. |
| instance_count | number | no | instance count used by this deterministic tool. |
| hourly_cost | number | no | hourly cost used by the calculation; monetary values are in USD unless stated otherwise. |
Use when a user asks about risk of a software purchase or SaaS commitment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monthlySubscription | number | yes | monthlySubscription used by this deterministic tool. |
| contractLengthMonths | number | no | contractLengthMonths used by this deterministic tool. |
| numUsers | number | no | numUsers used by this deterministic tool. |
| internalHourlyCost | number | no | internalHourlyCost used by this deterministic tool. |
| setupHours | number | no | setupHours used by this deterministic tool. |
| integrationCount | number | no | integrationCount used by this deterministic tool. |
| changeManagementRisk | number | no | changeManagementRisk used by this deterministic tool. |
| vendorStabilityScore | number | no | vendorStabilityScore used by this deterministic tool. |
Use when a user asks to estimate monthly cost of a Terraform plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| resource_type | string | yes | resource type used by this deterministic tool. |
| count | number | yes | count used by this deterministic tool. |
| instance_size | string | no | instance size used by this deterministic tool. |
Use when a user asks about TCO or multi-year SaaS cost.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseMonthlySubscription | number | no | baseMonthlySubscription used by this deterministic tool. |
| perUserMonthlyFee | number | no | perUserMonthlyFee used by this deterministic tool. |
| numPaidSeats | number | yes | numPaidSeats used by this deterministic tool. |
| expectedActiveUsers | number | yes | expectedActiveUsers used by this deterministic tool. |
| oneTimeFees | number | no | oneTimeFees used by this deterministic tool. |
| contractLength | number | no | contractLength used by this deterministic tool. |
| internalHourlyCost105 | number | no | internalHourlyCost105 used by this deterministic tool. |
| adminHoursPerMonth | number | no | adminHoursPerMonth used by this deterministic tool. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Utility Matrix or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Utility Matrix can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.