MIMF

SOFTWARE ENTITY · READ-ONLY TOOL BOUNDARY

What is Indie Metrics MCP?

Indie Metrics MCP is an open-source TypeScript server by Marco Hergi. It gives compatible AI assistants seven documented, read-only tools for asking questions about Stripe revenue, customers, products, subscriptions, transactions, refunds, and forecasts.

Project
Indie Metrics MCP
Category
Model Context Protocol server
Language
TypeScript
Tools
Seven
Data source
Stripe
Access model
Read-only, per README
npm status
Not published on July 27, 2026
Remote endpoint
Public synthetic endpoint available
01

Seven tools create a narrow data contract

The documented tools cover revenue summary, customer metrics, product performance, subscription health, recent transactions, refund analysis, and revenue forecasting.

The assistant does not receive an unrestricted instruction channel. It selects from named tools with defined business meaning.

02

Read-only design is the central boundary

The README states that the server never creates, modifies, or deletes Stripe data. It also states that the Stripe key remains local to the server process.

Read-only access reduces operational risk, but anyone connecting a real account should still protect the key, inspect the code, and use a restricted Stripe key with only the permissions the server requires.

03

Distribution is only partly complete

The package name indie-metrics-mcp returned HTTP 404 from the npm registry when checked on July 27, 2026. The repository is public, but the advertised package is not currently installable from npm.

A separate public Streamable HTTP endpoint now exposes all seven repository-aligned metric tools using bundled synthetic data, plus public search, fetch, and scenario comparison. It does not connect to Stripe and is not evidence that the repository's real-account integration is hosted or production-ready.

04

Why the architecture is useful

The reusable pattern is constrained tool mediation. Natural-language questions are translated into a small, inspectable set of operations instead of giving an assistant broad access to a business system.

This pattern is relevant to developers designing MCP servers for finance, operations, analytics, or other sensitive data.

05

Independent listings provide limited corroboration

PulseMCP and Glama list the server, while PolicyLayer publishes a tool-risk analysis. These sources support public discoverability, not an endorsement or a guarantee of security.

The GitHub repository remains authoritative for code, installation, licensing, and the current tool definitions.

SOURCE HIERARCHY

Verify at the origin.

The read-only statement comes from the current project README. The public benchmark records current evidence and gaps, but neither page audits the code or guarantees security, correctness, or suitability for a particular business.