mcpbeat Sign in

Agent Metering MCP Server

answering

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

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

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
11
Tools
read from the server
450 ms
Response time
average over 24h
0
Stars
last commit 18 Sep 2026

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Unsafe deserialization gateway/state_store.py:356
                state = pickle.loads(row[0])
Runs an external command mcp-publish/smoke_all.py:176
    r = subprocess.run([sys.executable, "-c", code], capture_output=True, text=True)
Page executes code built at runtime gateway/stats.html:191
  $("kpis").innerHTML = cells.map(([l,v,d]) =>
Dumps the whole environment growth-agent/growth_agent.py:512
        self.environ = dict(os.environ if environ is None else environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

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 356 ms 1 min ago

Alternatives to Agent Metering

same job, measured the same way
AgentIndex
by cognivis

Trust scores and on-chain payment receipts for x402 services.

4 tools answering
Xpay
by xona-labs

Xona Wallet: agent wallet for AI agents. x402 payments, AgenC hires, 20k+ services

335 installs/wk local only
Azeth Protocol
by azeth-protocol

Smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents

63 installs/wk local only
Verantis MCP
by m9labs-railscope

Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.

138 installs/wk 4 tools answering
Xero
by wyre-ai

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only
Xero
by wyre-technology

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only
Nutriref
by younghef

Pay-per-call USDA nutrition for AI agents (x402 micropayments in USDC on Base).

local only
Coinrailz
by tdnupe3

41 crypto micropayment services via x402 protocol

123 installs/wk local only

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 450 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 450 ms on average, which is faster than 33% 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?
We cannot say either way: written in Python, 0 stars on GitHub and 1 open issue, but we could not determine the licence, and without one the code is not open source by default.