MCP serverdev.pages.usage-lab/usage-lab
Record idempotent usage events and read monthly per-customer rollups (Usage Lab metering API).
Overview
Score?
UNRATED 0.143
of what a free look can see, on 5 looks
Looks
5
last 7 hr ago
Tools
6
More info
URL
usage-lab.pages.dev/mcp
streamable-http
Says it is
usage-lab 0.1.0
protocol 2025-06-18
In the record since
7 days ago
Among servers32,723 with a card
0median 0.547 · this server 0.143 · highest on record 0.8351
Toolsfrom sha256:94a7974d66…08358e
| Tool | Schema |
|---|---|
| create_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. acti |
input · no output |
| get_account Your account: plan, event and meter limits, event_count and first_event_at (GET /api/v1/account). Needs your API key. |
input · no output |
| get_docs 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 neede |
input · no output |
| get_meter_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. Ne |
input · no output |
| list_meters List the meters on your Usage Lab account (key, name, aggregation sum | count | unique_count). Needs your API key (Authorization: Bearer). |
input · no output |
| 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 |
input · no output |
Verify it yourself
npx teppi-check https://usage-lab.pages.dev/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M74JDYQQCQQH5VS5GJ6M9MNB