# lake-meter (npm · lake-meter)

Per-step model recommendations and cost estimates for coding-agent plans.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `lake-meter`: 71/100 (this document), [markdown](https://verifymcp.io/servers/getlake-lake-meter/lake-meter.md), [page](https://verifymcp.io/servers/getlake-lake-meter/lake-meter)

## Channel facts

- Registry: `npm`
- Package: `lake-meter`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 149 tokens (~74/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the lake-meter MCP server?

lake-meter runs locally as an npm package, launched with npx -y lake-meter mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add getlake-lake-meter -- npx -y lake-meter mcp
```

### Cursor

```json
{
  "mcpServers": {
    "getlake-lake-meter": {
      "command": "npx",
      "args": [
        "-y",
        "lake-meter",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "getlake-lake-meter": {
      "command": "npx",
      "args": [
        "-y",
        "lake-meter",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add getlake-lake-meter -- npx -y lake-meter mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "getlake-lake-meter": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lake-meter",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add getlake-lake-meter --command npx --arg -y --arg lake-meter --arg mcp
```

### Hermes

```yaml
mcp_servers:
  getlake-lake-meter:
    command: "npx"
    args: ["-y", "lake-meter", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "getlake-lake-meter": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lake-meter",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add getlake-lake-meter -t stdio -c npx -a -y lake-meter mcp
```

### Other

```json
{
  "mcpServers": {
    "getlake-lake-meter": {
      "command": "npx",
      "args": [
        "-y",
        "lake-meter",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 69, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-16 (score 57)

First indexed and scored.

## MCP tools (2)

### `estimate_plan` (~97 tokens)

Split a markdown implementation plan into steps, rate each step's complexity, recommend the cheapest model tier that should handle it, and estimate token and USD cost ranges per step and in total, compared with running everything on the top model. Heuristic estimate, not a measurement.

Input parameters:

- `plan` (string, required): The plan in markdown (numbered steps, headings or bullets).
- `provider` (string): Model family to recommend from. Default anthropic.

### `meter_status` (~52 tokens)

Measured spend of the current Claude Code run (tokens from the session transcript, priced at list price) and the active cap. Only works where the Lake Meter hooks are installed.

Input parameters:

- `session_id` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/getlake-lake-meter/lake-meter#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 57

## Common questions

### What is the lake-meter MCP server?

lake-meter is an MCP server listed in the public MCP registry as io.github.getlake/lake-meter. Per-step model recommendations and cost estimates for coding-agent plans. This page covers its npm package (lake-meter).

### Is the lake-meter MCP server safe to use?

lake-meter scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 lake-meter MCP server expose?

lake-meter exposes 2 tools: estimate_plan, meter_status. Their descriptions and schemas cost roughly 149 tokens of context every time the server is loaded.

### Is the lake-meter MCP server still maintained?

lake-meter is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the lake-meter MCP server under?

lake-meter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the lake-meter MCP server?

VerifyMCP ran 16 checks on lake-meter, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/lake-meter
- Socket report: https://socket.dev/npm/package/lake-meter
- Repository: https://github.com/getlake/lake-meter
- Website: https://getlake.github.io/lake-meter/
- Changelog RSS feed: https://verifymcp.io/servers/getlake-lake-meter/lake-meter.xml
- Changelog JSON feed: https://verifymcp.io/servers/getlake-lake-meter/lake-meter/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/getlake-lake-meter/lake-meter.json
- HTML version of this page: https://verifymcp.io/servers/getlake-lake-meter/lake-meter
