io.github.jdhart81/agent-metering
REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED SEP 20
Usage metering + SLA accounting for agent services (the meter behind x402 micropayments).
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 731 tokens (~66/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jdhart81/agent-metering MCP server?
io.github.jdhart81/agent-metering is a hosted endpoint at https://mcp.viridisconservation.com/metering/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.viridisconservation.com
claude mcp add --transport http jdhart81-agent-metering 'https://mcp.viridisconservation.com/metering/mcp'
{
"mcpServers": {
"jdhart81-agent-metering": {
"url": "https://mcp.viridisconservation.com/metering/mcp"
}
}
} {
"servers": {
"jdhart81-agent-metering": {
"type": "http",
"url": "https://mcp.viridisconservation.com/metering/mcp"
}
}
} [mcp_servers.jdhart81-agent-metering] url = "https://mcp.viridisconservation.com/metering/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jdhart81-agent-metering": {
"type": "remote",
"url": "https://mcp.viridisconservation.com/metering/mcp",
"enabled": true
}
}
} openclaw mcp add jdhart81-agent-metering --url 'https://mcp.viridisconservation.com/metering/mcp' --transport streamable-http
mcp_servers:
jdhart81-agent-metering:
url: "https://mcp.viridisconservation.com/metering/mcp" {
"McpServers": {
"jdhart81-agent-metering": {
"Transport": "http",
"Url": "https://mcp.viridisconservation.com/metering/mcp"
}
}
} assistant mcp add jdhart81-agent-metering -t streamable-http -u 'https://mcp.viridisconservation.com/metering/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Authorization: unverified → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.viridisconservation.com/metering/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.viridisconservation.com | CN=YE1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5abb43a3acf241ca07b1eb9ff25cafac4e4 |
| SANs: mcp.viridisconservation.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.viridisconservation.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| viridisconservation.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.viridisconservation.com/metering/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/metering/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/metering/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
close_period ~44
Freeze all open events into an immutable invoice (exactly-once). The invoice amount is what agent-escrow-agent should settle.
| Name | Type | Req | Description |
|---|---|---|---|
| meter_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_meter ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer | string | yes | – |
| currency | string | – | – |
| price_minor_per_unit | number | yes | – |
| provider | string | yes | – |
| sla_target | number | – | – |
| unit | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent ~13
Fleet-standard self-description.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
flag_meter ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | – |
| is_test | boolean | yes | – |
| meter_id | string | yes | – |
| note | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_events ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | – | – | – |
| consumer_class | – | – | – |
| cursor | – | – | – |
| include_test | boolean | – | – |
| limit | integer | – | – |
| meter_id | – | – | – |
| outcome | – | – | – |
| provider | – | – | – |
| since | – | – | – |
| until | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_meters ~18
List all meters with event/invoice counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
record_usage ~81
Record a usage event. Idempotent on event_id (safe to retry — never double-billed). outcome is 'ok' or 'error' and feeds the SLA report.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| metadata | – | – | – |
| meter_id | string | yes | – |
| outcome | string | – | – |
| quantity | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sla_report ~32
Pure SLA report: success_rate vs sla_target, breach flag. No mutation.
| Name | Type | Req | Description |
|---|---|---|---|
| meter_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
usage_summary ~32
Totals for a meter: event count, total quantity, accrued minor units.
| Name | Type | Req | Description |
|---|---|---|---|
| meter_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
usage_timeseries ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | – |
| channel | – | – | – |
| consumer_class | – | – | – |
| include_test | boolean | – | – |
| meter_id | – | – | – |
| provider | – | – | – |
| since | – | – | – |
| until | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_chain ~30
Verify the tamper-evident event hash chain for a meter.
| Name | Type | Req | Description |
|---|---|---|---|
| meter_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.jdhart81/agent-metering MCP server?
io.github.jdhart81/agent-metering is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-metering. Usage metering + SLA accounting for agent services (the meter behind x402 micropayments). This page covers its hosted endpoint (https://mcp.viridisconservation.com/metering/mcp).
Is the io.github.jdhart81/agent-metering MCP server safe to use?
io.github.jdhart81/agent-metering scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jdhart81/agent-metering MCP server expose?
io.github.jdhart81/agent-metering exposes 11 tools: create_meter, record_usage, usage_summary, sla_report, close_period, and 6 more. Their descriptions and schemas cost roughly 709 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-metering MCP server require authentication?
Yes. io.github.jdhart81/agent-metering asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.jdhart81/agent-metering MCP server still maintained?
io.github.jdhart81/agent-metering is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.