Skip to content

Usage Lab MCP server

dev.pages.usage-lab/usage-labusage-lab.pages.devstreamable-httpv0.1.0Scanned

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

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Usage Lab MCP server can do

The Usage Lab MCP server is published by usage-lab.pages.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: create_meter and record_usage_events), but cannot delete data. 4 tools only read.

1 tool reads private data (get_docs).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • create_meterCreate a meter once (POST /api/v1/meters).No findings

    Why it is in this group

    • The name "create_meter" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a meter
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • record_usage_eventsRecord 1-100 usage events in one all-or-nothing batch (POST /api/v1/usage).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Record usage events
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • get_accountYour account: plan, event and meter limits, event_count and first_event_at (GET /api/v1/account).No findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.
    Description, as the server wrote it
    Your account: plan, event and meter limits, event_count and first_event_at (GET /api/v1/account). Needs your API key.

    Annotations the server declares

    • title: Get account
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_docsQuickstart 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.Reads private dataNo findings

    Why it is in this group

    • The name "get_docs" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_docs" says "get" and "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Usage Lab quickstart
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_meter_rollupsMonthly totals per customer for one meter, recomputed from raw events (GET /api/v1/meters/{meter}/rollups).No findings

    Why it is in this group

    • The name "get_meter_rollups" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get monthly rollups
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_metersList the meters on your Usage Lab account (key, name, aggregation sum | count | unique_count).No findings

    Why it is in this group

    • The name "list_meters" says "list": a word for reading.
    Description, as the server wrote it
    List the meters on your Usage Lab account (key, name, aggregation sum | count | unique_count). Needs your API key (Authorization: Bearer).

    Annotations the server declares

    • title: List meters
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:21 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://usage-lab.pages.dev/mcp: tools/list returned 6 tools to an anonymous client, including create_meter (write), record_usage_events (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http usage-lab https://usage-lab.pages.dev/mcp
claude mcp add --transport http usage-lab https://usage-lab.pages.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__usage-lab__get_docs",
      "mcp__usage-lab__list_meters",
      "mcp__usage-lab__get_meter_rollups",
      "mcp__usage-lab__get_account"
    ],
    "ask": [
      "mcp__usage-lab__create_meter",
      "mcp__usage-lab__record_usage_events"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as usage-lab. Review it before you use it.

Capability tags behind 1 rule
  • mcp__usage-lab__get_docs private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.pages.usage-lab/usage-lab/verify?hash=1a5cee051237558e74b69e68568c2c6c0d7de2489d4b4dff99f9f40111abad67" | jq -e '.changed == false'

Pinned hash 1a5cee051237, from Nov 11, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.pages.usage-lab/usage-lab/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.pages.usage-lab/usage-lab
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.pages.usage-lab/usage-lab.svg)](https://radar.anlyon.com/servers/dev.pages.usage-lab/usage-lab)

Source: MCP Registry. Synced Nov 11, 2026, 01:17 UTC.

Usage Lab MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Usage Lab MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Usage Lab MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Usage Lab MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Usage Lab MCP server have?

6 tools: 2 write, 4 read. create_meter, record_usage_events, get_docs, list_meters, get_meter_rollups and get_account.

Does the Usage Lab MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Usage Lab MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Usage Lab MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.