MCP.Market

Finops Focus MCP server

by aaronmsoto·io.github.aaronmsoto/finops-focus-mcp·v0.2.0

Unofficial MCP server for the FOCUS spec: columns, attributes, requirements, cross-version diffs.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
New

0 stars0 downloads/wk

Reviews

Write one

Nobody has reviewed Finops Focus yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Finops Focus tools (9)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • calculate_kpi

    UNOFFICIAL: computes one of the KPIs from get_kpi_mapping using this server's own derived FOCUS-terms

  • compare_versions

    The …→… column diff — an UNOFFICIAL derivation computed by this server from the two tagged spec releases, source-cited per entry. Without `column`: the full diff (… added, … removed, … changed). With `column`: that one column's status and detail.

  • get_attribute

    Full record for one cross-cutting FOCUS attribute (naming/formatting conventions like currency codes, datetime format, key-value format): description, normative requirements, exceptions. Look up by the `attribute` parameter — an attribute ID or its lowercase slug, e.g. 'datetime_format'. Attribute names can change between versions; discover current slugs via search_focus with entity_types=['attrib

  • get_column

    Full record for one FOCUS column: description, content constraints (type, feature level, nulls, data type, value format), allowed values, normative requirements, and the version it was introduced in. Look up by the `column` parameter — a Column ID or its lowercase slug, e.g. 'BilledCost'.

  • get_kpi_mapping

    UNOFFICIAL, derived-by-this-server mapping from framework KPIs (effective savings rate, commitment

  • get_requirements

    The normative MUST/SHOULD bullets for one column, verbatim from the spec text (plus source_url/license attribution). Use get_column for the full record.

  • list_columns

    All columns for one spec version, optionally filtered by feature_level (Mandatory|Conditional|Recommended) or column_type (Metric|Dimension); the extra enum value 'unknown' is a crawler parse fallback that matches no column in the shipped data. Default limit returns the full list in one call (…).

  • list_versions

    Every FOCUS spec version this server serves, with its source git tag and column/attribute counts. Start here to discover valid `version` values for the other tools. No parameters.

  • search_focus

    Ranked keyword search over one spec version's columns and attributes. Returns slug + uri per hit — feed into get_column/get_attribute. Use when you don't already know a Column ID.

Public scan report

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan45 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Finops Focus compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
9
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 9 read

Install Finops Focus in Claude Code, Cursor or VS Code

Runs npx -y finops-focus-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add finops-focus-mcp -- npx -y finops-focus-mcp
Add to Cursor

What the publisher says

From the Finops Focus repository's README, as published. We do not edit it. Read it on GitHub

finops-framework-mcp

Three unofficial MCP servers that give AI assistants a structured, sourced interface to published FinOps and AI-cost guidance, so an assistant answers with the publishers' actual text and formulas instead of improvising:

All three are read-only (an agent can read guidance, never change your practice or data) and offline once installed (no network access at runtime, no telemetry). Use any one on its own; together they cover what good looks like, which billing columns prove it, and what drives AI token cost.

Start here: the usage guide

aaronmsoto.github.io/finops-framework-mcp is a free, no-install walkthrough written for FinOps practitioners as much as engineers. It explains what each server does, connects them to Claude in a couple of minutes, and works through five examples, from a showback report to whether prompt caching is paying off. Every number and quote in it comes from a real run of these servers. See Documentation for the page list.

Why this exists

Ask an AI assistant "how mature is our Allocation practice?", "which FOCUS columns feed Effective Savings Rate?" or "is our prompt caching paying off?" without these servers, and it will happily improvise a plausible answer. With them, every response is the publisher's own text and formulas, structured for an assistant to read, with the source URL and license attached.

Anything a server had to work out itself is labeled, never passed off as published guidance:

cross-version diff are marked UNOFFICIAL (official: false).

  • The FOCUS server's KPI-to-column mapping, computed KPI values and

answer, because most Tokenomics Foundation guidance is a working draft or release candidate. Its curated crosswalk is unofficial and only appears with FINOPSMCPEXPERIMENTAL=1.

  • The tokenomics server states each source's publication status on every

relationships between capabilities, no maturity levels beyond the Foundation's Crawl/Walk/Run.

  • The framework server is official-only out of the box: no invented

Quickstart

All three are on npm, so there is nothing to clone or build. Each package ships its own data and runs offline. Node >= 22 is the only requirement.

npx -y finops-framework-mcp
npx -y finops-focus-mcp
npx -y tokenomics-overview-mcp

(-y skips npx's first-run install prompt, which can hang non-interactive MCP clients. Pin a version with, for example, npx -y finops-focus-mcp@0.2.)

Claude Code:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Finops Focus: common questions

Is Finops Focus MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Finops Focus safety report
How do I install Finops Focus?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Finops Focus need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is Finops Focus maintained?
The last commit was 15 days ago (2026-10-20). The latest release is v0.2.0.
How does Finops Focus compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 9 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from aaronmsoto →