Skip to content

Agent Metering MCP server

io.github.jdhart81/agent-meteringjdhart81streamable-httpv0.2.1Scanned

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

11 tools: 1 can delete or cancel things, 7 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • 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 Agent Metering MCP server can do

The Agent Metering MCP server is published by the GitHub account jdhart81. It has 11 tools. It can delete or cancel things (1 tool: close_period) and create or change data (7 tools: create_meter, record_usage, usage_summary, sla_report and 3 more). 3 tools only read.

1 tool can send data out of your system (usage_timeseries).

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, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 0.2.1.

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.

11 tools

Deletes or cancels 1Claude Code: deny
  • close_periodFreeze all open events into an immutable invoice (exactly-once).No findings

    Why it is in this group

    • The name "close_period" says "close": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Freeze all open events into an immutable invoice (exactly-once). The invoice amount is what agent-escrow-agent should settle.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Close period
Changes things 7Claude Code: ask
  • create_meterCreate a usage meter between a provider and a consumer agent.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 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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Create meter
  • flag_meterAdmin: flag/unflag a meter as test/synthetic so its events are excluded from usage statistics by default.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
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Flag meter
  • record_usageRecord a usage event.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 a usage event. Idempotent on event_id (safe to retry — never double-billed). outcome is 'ok' or 'error' and feeds the SLA report.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Record usage
  • sla_reportPure SLA report: success_rate vs sla_target, breach flag.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Pure SLA report: success_rate vs sla_target, breach flag. No mutation.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Sla report
  • usage_summaryTotals for a meter: event count, total quantity, accrued minor units.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Totals for a meter: event count, total quantity, accrued minor units.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Usage summary
  • usage_timeseriesUsage 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…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a destination (input.channel): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Usage timeseries
  • verify_chainVerify the tamper-evident event hash chain for a meter.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify the tamper-evident event hash chain for a meter.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Verify chain
Only reads 3Show 3 read-only tools
  • describe_agentDescribe this agent: name, version, purpose, every action it supports and the inputs each one takes.No findings

    Why it is in this group

    • The name "describe_agent" says "describe": a word for reading.
    Description, as the server wrote it
    Describe this agent: name, version, purpose, every action it supports and the inputs each one takes. Read-only and free; call it first to learn how to use this server.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Describe this service
  • list_eventsRead usage events (paginated, read-only).No findings

    Why it is in this group

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

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List events
  • list_metersList all meters with event/invoice counts.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 all meters with event/invoice counts.

    Annotations the server declares

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

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 private-data or untrusted-input.

Reads private data0
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 out1
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 20, 2026, 19:26 UTC, unchanged since Oct 22, 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
8
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
  • HighThe whole server

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

    Matched text

    https://mcp.viridisconservation.com/metering/mcp: tools/list returned 11 tools to an anonymous client, including close_period (destructive), create_meter (write), record_usage (write), usage_summary (write), sla_report (write) and 3 more

    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.

  1. Tools9 changed.~9 changedView diff
  2. Tools11 changed.~11 changedView diff

Install

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

claude mcp add --transport http agent-metering https://mcp.viridisconservation.com/metering/mcp
claude mcp add --transport http agent-metering https://mcp.viridisconservation.com/metering/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__agent-metering__list_meters",
      "mcp__agent-metering__list_events",
      "mcp__agent-metering__describe_agent"
    ],
    "ask": [
      "mcp__agent-metering__create_meter",
      "mcp__agent-metering__record_usage",
      "mcp__agent-metering__usage_summary",
      "mcp__agent-metering__sla_report",
      "mcp__agent-metering__verify_chain",
      "mcp__agent-metering__usage_timeseries",
      "mcp__agent-metering__flag_meter"
    ],
    "deny": [
      "mcp__agent-metering__close_period"
    ]
  }
}

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 agent-metering. Review it before you use it.

Capability tags behind 1 rule
  • mcp__agent-metering__usage_timeseries outbound

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/io.github.jdhart81/agent-metering/verify?hash=04d004aa32eb8330f6161b7ce1f01648de714445eb014e3f0c063a11d21226be" | jq -e '.changed == false'

Pinned hash 04d004aa32eb, from Nov 16, 2026, 02:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.jdhart81/agent-metering/changes.xml

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

Badge

Anlyon Radar badge for io.github.jdhart81/agent-metering
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.jdhart81/agent-metering.svg)](https://radar.anlyon.com/servers/io.github.jdhart81/agent-metering)

Source: MCP Registry · repository. Synced Nov 16, 2026, 02:17 UTC.

Agent Metering MCP server: questions and answers

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

Is the Agent Metering MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 8 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 Agent Metering MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: close_period.

Can the Agent Metering 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 Agent Metering MCP server have?

11 tools: 1 destructive, 7 write, 3 read. close_period, create_meter, record_usage, usage_summary, sla_report, verify_chain, usage_timeseries, flag_meter and 3 more.

Does the Agent Metering MCP server need sign-in or OAuth?

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

Does the Agent Metering MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): usage_timeseries.

Has the Agent Metering MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.