# Usage Lab (remote · usage-lab.pages.dev)

Record idempotent usage events and read monthly per-customer rollups (Usage Lab metering API).

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `usage-lab.pages.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/dev-pages-usage-lab-usage-lab/usage-lab.md), [page](https://verifymcp.io/servers/dev-pages-usage-lab-usage-lab/usage-lab)

## Channel facts

- Endpoint: `https://usage-lab.pages.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 560 tokens (~93/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Usage Lab MCP server?

Usage Lab is a hosted endpoint at https://usage-lab.pages.dev/mcp, so there is nothing to install locally. 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 --transport http dev-pages-usage-lab-usage-lab 'https://usage-lab.pages.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-pages-usage-lab-usage-lab": {
      "url": "https://usage-lab.pages.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-pages-usage-lab-usage-lab": {
      "type": "http",
      "url": "https://usage-lab.pages.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-pages-usage-lab-usage-lab]
url = "https://usage-lab.pages.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-pages-usage-lab-usage-lab": {
      "type": "remote",
      "url": "https://usage-lab.pages.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-pages-usage-lab-usage-lab --url 'https://usage-lab.pages.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-pages-usage-lab-usage-lab:
    url: "https://usage-lab.pages.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-pages-usage-lab-usage-lab": {
      "Transport": "http",
      "Url": "https://usage-lab.pages.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-pages-usage-lab-usage-lab -t streamable-http -u 'https://usage-lab.pages.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-pages-usage-lab-usage-lab": {
      "type": "http",
      "url": "https://usage-lab.pages.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-19 (score 74, +1)

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

### 2026-11-17 (score 73, +1)

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

### 2026-11-15 (score 72, +1)

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

### 2026-11-13 (score 71, +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-12 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 70)

First indexed and scored.

## MCP tools (6)

### `get_docs` (~52 tokens)

Usage Lab quickstart

Quickstart for the Usage Lab metering API and this MCP server: how to get a free API key, connect, create a meter, record idempotent usage events and read rollups. No API key needed.

### `list_meters` (~40 tokens)

List meters

List the meters on your Usage Lab account (key, name, aggregation sum | count | unique_count). Needs your API key (Authorization: Bearer).

### `create_meter` (~155 tokens)

Create a meter

Create a meter once (POST /api/v1/meters). aggregation: sum (add up value, e.g. tokens), count (number of events, e.g. tool calls) or unique_count (distinct unique_value, e.g. active users). Re-creating an existing key returns meter_exists (harmless). Free plan: 3 meters. Needs your API key.

Input parameters:

- `aggregation` (string, required)
- `key` (string, required): 1-64 chars of letters, digits, _ . - (e.g. agent_tool_calls).
- `name` (string): Optional display name (defaults to key).
- `stripe_event_name` (string): Optional Stripe Billing Meter event_name for Stripe push (Pro/Ultra).

### `record_usage_events` (~72 tokens)

Record usage events

Record 1-100 usage events in one all-or-nothing batch (POST /api/v1/usage). Every event MUST carry its own idempotency_key; retrying with the same keys is safe (results say created / duplicate / conflict). Needs your API key.

Input parameters:

- `events` (array, required)

### `get_meter_rollups` (~96 tokens)

Get monthly rollups

Monthly totals per customer for one meter, recomputed from raw events (GET /api/v1/meters/{meter}/rollups). Returns total_quantity and per-subscription quantity and event_count. Needs your API key.

Input parameters:

- `meter` (string, required): Meter key or id.
- `month` (string): YYYY-MM (UTC). Defaults to the current month.
- `subscription` (string): Optional: only this customer/subscription.

### `get_account` (~37 tokens)

Get account

Your account: plan, event and meter limits, event_count and first_event_at (GET /api/v1/account). Needs your API key.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-pages-usage-lab-usage-lab/usage-lab#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70

## Common questions

### What is the Usage Lab MCP server?

Usage Lab is an MCP server listed in the public MCP registry as dev.pages.usage-lab/usage-lab. Record idempotent usage events and read monthly per-customer rollups (Usage Lab metering API). This page covers its hosted endpoint (https://usage-lab.pages.dev/mcp).

### Is the Usage Lab MCP server safe to use?

Usage Lab scores 74 out of 100 on VerifyMCP. 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 Usage Lab MCP server expose?

Usage Lab exposes 6 tools: get_docs, list_meters, create_meter, record_usage_events, get_meter_rollups, get_account. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.

### Does the Usage Lab MCP server require authentication?

No. We connected to Usage Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Usage Lab MCP server still maintained?

Usage Lab 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 did VerifyMCP test on the Usage Lab MCP server?

VerifyMCP ran 13 checks on Usage Lab, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://usage-lab.pages.dev/mcp
- Website: https://usage-lab.pages.dev/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/dev-pages-usage-lab-usage-lab/usage-lab.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-pages-usage-lab-usage-lab/usage-lab/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-pages-usage-lab-usage-lab/usage-lab.json
- HTML version of this page: https://verifymcp.io/servers/dev-pages-usage-lab-usage-lab/usage-lab
