# io.github.jdhart81/agent-metering (remote · mcp.viridisconservation.com)

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

- Trust score: 71/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.viridisconservation.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/jdhart81-agent-metering/metering-mcp.md), [page](https://verifymcp.io/servers/jdhart81-agent-metering/metering-mcp)

## Channel facts

- Endpoint: `https://mcp.viridisconservation.com/metering/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 731 tokens (~66/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http jdhart81-agent-metering https://mcp.viridisconservation.com/metering/mcp
```

### Codex

```toml
[mcp_servers.jdhart81-agent-metering]
url = "https://mcp.viridisconservation.com/metering/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jdhart81-agent-metering": {
      "type": "remote",
      "url": "https://mcp.viridisconservation.com/metering/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jdhart81-agent-metering --url https://mcp.viridisconservation.com/metering/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jdhart81-agent-metering:
    url: "https://mcp.viridisconservation.com/metering/mcp"
```

### Other

```json
{
  "mcpServers": {
    "jdhart81-agent-metering": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 70, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 63, +7)

- [security regression] Authorization: unverified → fail

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (11)

### `create_meter` (~103 tokens)

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.

Input parameters:

- `consumer` (string, required)
- `currency` (string)
- `price_minor_per_unit` (number, required)
- `provider` (string, required)
- `sla_target` (number)
- `unit` (string, required)

Output parameters:

- `result` (string)

### `record_usage` (~81 tokens)

Record a usage event. Idempotent on event_id (safe to retry — never
    double-billed). outcome is 'ok' or 'error' and feeds the SLA report.

Input parameters:

- `event_id` (string, required)
- `metadata`
- `meter_id` (string, required)
- `outcome` (string)
- `quantity` (number, required)

Output parameters:

- `result` (string)

### `usage_summary` (~32 tokens)

Totals for a meter: event count, total quantity, accrued minor units.

Input parameters:

- `meter_id` (string, required)

Output parameters:

- `result` (string)

### `sla_report` (~32 tokens)

Pure SLA report: success_rate vs sla_target, breach flag. No mutation.

Input parameters:

- `meter_id` (string, required)

Output parameters:

- `result` (string)

### `close_period` (~44 tokens)

Freeze all open events into an immutable invoice (exactly-once).
    The invoice amount is what agent-escrow-agent should settle.

Input parameters:

- `meter_id` (string, required)

Output parameters:

- `result` (string)

### `verify_chain` (~30 tokens)

Verify the tamper-evident event hash chain for a meter.

Input parameters:

- `meter_id` (string, required)

Output parameters:

- `result` (string)

### `list_meters` (~18 tokens)

List all meters with event/invoice counts.

Output parameters:

- `result` (string)

### `list_events` (~129 tokens)

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.

Input parameters:

- `channel`
- `consumer_class`
- `cursor`
- `include_test` (boolean)
- `limit` (integer)
- `meter_id`
- `outcome`
- `provider`
- `since`
- `until`

Output parameters:

- `result` (string)

### `usage_timeseries` (~131 tokens)

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.

Input parameters:

- `bucket` (string)
- `channel`
- `consumer_class`
- `include_test` (boolean)
- `meter_id`
- `provider`
- `since`
- `until`

Output parameters:

- `result` (string)

### `flag_meter` (~96 tokens)

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.

Input parameters:

- `admin_token` (string, required)
- `is_test` (boolean, required)
- `meter_id` (string, required)
- `note` (string)

Output parameters:

- `result` (string)

### `describe_agent` (~13 tokens)

Fleet-standard self-description.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jdhart81-agent-metering/metering-mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 71
- 2026-08-01: 70
- 2026-07-31: 70
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://mcp.viridisconservation.com/metering/mcp
- Repository: https://github.com/jdhart81/viridis-agent-fleet
- Changelog RSS feed: https://verifymcp.io/servers/jdhart81-agent-metering/metering-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/jdhart81-agent-metering/metering-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/jdhart81-agent-metering/metering-mcp