Index / MCP servers / Agent Metering

Agent Metering MCP server

Connect Agent Metering and your agent gets 11 tools, among them close_period, create_meter, describe_agent. It answers at https://mcp.viridisconservation.com/metering/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

Status
Answering
Tools
11
Reliability
6 of 6 checks
Response time
300 ms
Transport
streamable HTTP
Last checked
22 October 2026

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

Description as the publisher wrote it.

The 11 tools Agent Metering offers

ToolWhat it does
close_periodFreeze all open events into an immutable invoice (exactly-once). The invoice amount is what agent-escrow-agent should settle.
Inputs: meter_id
create_meterCreate 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.
Inputs: provider, consumer, unit, price_minor_per_unit, currency, sla_target
describe_agentFleet-standard self-description.
flag_meterAdmin: 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.
Inputs: meter_id, is_test, admin_token, note
list_eventsRead 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. Retu
Inputs: meter_id, provider, consumer_class, channel, outcome, since
list_metersList all meters with event/invoice counts.
record_usageRecord a usage event. Idempotent on event_id (safe to retry — never double-billed). outcome is 'ok' or 'error' and feeds the SLA report.
Inputs: meter_id, event_id, quantity, outcome, metadata
sla_reportPure SLA report: success_rate vs sla_target, breach flag. No mutation.
Inputs: meter_id
usage_summaryTotals for a meter: event count, total quantity, accrued minor units.
Inputs: meter_id
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. Includes per-bucket breakdowns by consumer_class / channel
Inputs: bucket, provider, meter_id, consumer_class, channel, since
verify_chainVerify the tamper-evident event hash chain for a meter.
Inputs: meter_id

Add Agent Metering to your AI client

Every block below points at https://mcp.viridisconservation.com/metering/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http agent-metering https://mcp.viridisconservation.com/metering/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "agent-metering": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.viridisconservation.com/metering/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "agent-metering": {
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "agent-metering": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "agent-metering": {
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "agent-metering": {
      "serverUrl": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "agent-metering": {
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Agent Metering
version: 0.0.1
schema: v1
mcpServers:
  - name: Agent Metering
    type: streamable-http
    url: https://mcp.viridisconservation.com/metering/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "agent-metering": {
      "httpUrl": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "agent-metering": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "agent-metering": {
      "url": "https://mcp.viridisconservation.com/metering/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.viridisconservation.com%2Fmetering%2Fmcp&type=streamable_http&id=agent-metering&name=Agent%20Metering

Is Agent Metering up right now?

It answered our last check on 22 October 2026 in 300 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Agent Metering

Questions about Agent Metering

How many tools does Agent Metering have?

11, as returned by the server's own tools/list on 14 September 2026: close_period, create_meter, describe_agent, flag_meter, list_events, list_meters, record_usage, sla_report, and 3 more.

Is Agent Metering down?

It answered our last check on 22 October 2026 in 300 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Agent Metering to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.viridisconservation.com/metering/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Agent Metering need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.jdhart81. Endpoint host: mcp.viridisconservation.com. ARD identifier: urn:air:io.github.jdhart81:mcp:agent-metering. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.