MCP.Market

Ezstat MCP server

by ezstat.dev·dev.ezstat/ezstat-mcp-server·v0.7.0
No reviews yet

Track and query EzStat metrics from Claude, Cursor, or any MCP agent. StatHat-compatible.

B74/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B74/100

full report

Adoption
Growing

0 stars65 downloads/wk

Reviews

Write one

Nobody has reviewed Ezstat yet.

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

Ezstat tools (7, 2 write)

write = sends, deletes, buys or posts

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

  • ask_ezstat

    Ask a natural-language question about the account's metrics. This is the agent-read path: send a question like "what spiked yesterday?" or "compare signups vs cancellations last 7 days" and EzStat returns a grounded answer plus the underlying data it used.

  • create_alertwrite action

    Create an alert on a stat: webhook fires when the condition is met (above/below threshold, % change, heartbeat/missing data, sustained). Deliveries retry with backoff and carry a stable idempotency_key so receivers can dedup. The stat is referenced by NAME; it must already exist.

  • delete_alertwrite action

    Delete an alert by id (see list_alerts).

  • list_alerts

    List the account's alerts: id, stat, condition, channel, enabled, last trigger time.

  • list_stats

    List the account's metrics — names and types. Call this first when you don't know what stats exist in the account.

  • read_stat

    Read a single stat: latest value, recent series, and basic summary (count/min/max/avg/sum). Use this for a structured read of one metric — prefer `ask_ezstat` for free-form questions over many stats.

  • track_metric

    Record a metric point your app "produced". Use this whenever the surrounding code emits a counter or gauge — e.g. on a page view, a successful checkout, or a measured latency. Counters are +N (default +1), values are gauges (e.g. 42.5 ms).

Public scan report

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

no findings
  • Code scan10 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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 56 days ago12/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace5/10
Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Ezstat compares

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

Safety score
74/100
higher than 43% of 4,460 AI and agents servers
Tools
7
the typical AI and agents server has 6
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
65
more than 52% of 1,538 AI and agents servers with a package

What its tools let an agent do: 5 read · 1 create · 1 delete

Install Ezstat in Claude Code, Cursor or VS Code

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

claude mcp add ezstat-mcp-server -- npx -y ezstat-mcp-server
Add to Cursor

What the publisher says

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

EzStat MCP Server

A standalone Model Context Protocol server for EzStat. Let Claude / Cursor / any MCP-compatible agent push and read your metrics natively — no copy-paste, no dashboard hop. This is the product behind the "metrics your agents write and read themselves" positioning: every agent that touches your code can also touch your observability.

The server speaks stdio (the standard transport for local agent runners) and — as a hosted endpoint at https://mcp.ezstat.dev — streamable HTTP, exposing the same seven focused tools. Each tool description is written for an agent audience so the model knows when to call it.

Hosted endpoint — zero install

Agents can connect to the hosted streamable-HTTP endpoint with nothing but an EzStat API key — no npm install, no local process:

{
  "mcpServers": {
    "ezstat": {
      "type": "http",
      "url": "https://mcp.ezstat.dev",
      "headers": {
        "Authorization": "Bearer ezkey_your_api_key_here"
      }
    }
  }
}

the server holds no key of its own and each connection only ever sees its own account.

  • Multi-tenant: every request carries your key as Authorization: Bearer ;

registry inspectors can introspect the tool surface before you configure anything.

  • Discovery is free: initialize and tools/list work without a key, so clients and

clean in-band MCP tool error telling the agent what to send — never a hang or a crash.

  • Tool calls require the key: a call without one (or with an invalid one) returns a
  • Stateless: no sessions are issued or required; each POST is self-contained.

This hosted endpoint also satisfies the requirements for hosted/remote listings on MCP registries (e.g. Smithery's hosted-server path) — see server.json's remotes entry.

The stdio transport below remains fully supported and is still the right choice when you want the server running locally under your own runner.

Tools

Tool descriptions are tuned for agent reasoning — see src/server.ts.

Install (Claude Desktop / Claude Code / Cursor)

One-line install (npm/pnpm)

# pnpm
pnpm add -g ezstat-mcp-server

# npm
npm install -g ezstat-mcp-server

Configure the MCP client

Claude Desktop (~/.config/Claude/claudedesktopconfig.json on macOS/Linux, %APPDATA%\Claude\claudedesktopconfig.json on Windows):

{
  "mcpServers": {
    "ezstat": {
      "command": "ezstat-mcp-server",
      "env": {
        "EZSTAT_API_KEY": "ezkey_your_api_key_here"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "ezstat": {
      "command": "ezstat-mcp-server",
      "env": {
        "EZSTAT_API_KEY": "ezkey_your_api_key_here"
      }
    }
  }
}

Get your API key from (it's the "ezkey").

Smithery

Shortened. The full README is on GitHub.

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

Ezstat: common questions

Is Ezstat MCP server safe?
Mostly: it is graded B (74/100). Read the Ezstat safety report
How do I install Ezstat?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Ezstat need an API key?
Yes. The registry entry asks for EZSTAT_API_KEY.
Is Ezstat maintained?
The last commit was 56 days ago (2026-09-09). The latest release is v0.7.0.
What can I use instead of Ezstat?
Servers from other publishers that do the same job: Memanto MCP server, Emilia Protocol MCP server and Superlog MCP server.
How does Ezstat compare with other AI and agents MCP servers?
safety score 74/100 (higher than 43% of 4,460 AI and agents servers); tools 7 (the typical AI and agents server has 6); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Ezstat

Same job from other publishers: the closest match first, then the best rated.

  • Memanto
    MCP server for Memanto - persistent semantic memory for any MCP-compatible agent
    A
  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • Superlog
    Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
    A
  • Agent Recall
    Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
    A
  • freellmpool
    OpenAI-compatible MCP gateway cataloging 22 LLM providers, with routing, failover, and tools.
    A