mcpbeat

Agent Metering MCP Server

io.github.jdhart81/agent-metering
answering

Agent Metering is answering right now. Last checked 1 min ago. It exposes 11 tools. Last commit 3 Aug 2026.

Usage metering + SLA accounting for agent services (the meter behind x402 micropayments).

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
92 of 92 checks
11
Tools
read from the server
353 ms
Response time
average over 24h
0
Stars
last commit 3 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add agent-metering --transport http https://mcp.viridisconservation.com/metering/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-metering": {
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-metering]
url = "https://mcp.viridisconservation.com/metering/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-metering": {
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-metering": {
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

usage
usage_summary
Totals for a meter: event count, total quantity, accrued minor units.
usage_timeseries
Usage time series bucketed on each event's recorded_at (UTC; bucket=day|hour), grouped across meters by provider — a real time-series primitive, independent of meter creation times. Includes per-bucket breakdowns by consumer_class / channel / provider. est_accrued_minor is an estimate; authoritative billing stays with usage_summary.
close
close_period
Freeze all open events into an immutable invoice (exactly-once). The invoice amount is what agent-escrow-agent should settle.
describe
describe_agent
Fleet-standard self-description.
events
list_events
Read usage events (paginated, read-only). Filter by meter, provider, consumer_class (internal|external|unknown), channel, outcome (ok|error), and ISO date range [since, until). Test-flagged events are excluded unless include_test=true. Returns events + next_cursor.
flag
flag_meter
Admin: flag/unflag a meter as test/synthetic so its events are excluded from usage statistics by default. Touches meter metadata only — never events, never the hash chain, never billing accruals. Requires the server's VIRIDIS_ADMIN_TOKEN.
meter
create_meter
Create a usage meter between a provider and a consumer agent. unit: what is being counted (call, token, kwh, ...). Price is in minor currency units (cents) per unit. Returns the meter_id.
meters
list_meters
List all meters with event/invoice counts.
record
record_usage
Record a usage event. Idempotent on event_id (safe to retry — never double-billed). outcome is 'ok' or 'error' and feeds the SLA report.
sla
sla_report
Pure SLA report: success_rate vs sla_target, breach flag. No mutation.
verify
verify_chain
Verify the tamper-evident event hash chain for a meter.

Endpoints

URLTransportStateLatencyChecked
https://mcp.viridisconservation.com/metering/mcp streamable-http answering 323 ms 1 min ago

Agent Metering — questions

Answers built from our own checks of this server.

What can Agent Metering do?
It exposes 11 tools, read directly from the server on our last check. Among them: close_period, create_meter, describe_agent, flag_meter, list_events, list_meters and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agent Metering working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 353 ms. The bar chart above shows every period we have measured.
How do I connect Agent Metering?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Metering need an API key?
No. Agent Metering completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Metering?
It answers our handshake in 353 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Agent Metering open source?
Yes — written in Python, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.