io.github.jdhart81/agent-metering MCP Server
io.github.jdhart81/agent-metering
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.jdhart81/agent-metering MCP server?
Usage metering + SLA accounting for agent services (the meter behind x402 micropayments).
How to install io.github.jdhart81/agent-metering
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"agent-metering": {
"url": "https://mcp.viridisconservation.com/metering/mcp"
}
}
}Related MCP servers

Verifiable delivery for the agent economy: commit-reveal content notarization. Sellers commit to a d
Verified conservation credits matched to agent compute emissions — the conservation flywheel of the
Genesis certificates, lineage, and cascading recalls: birth certificates + bloodlines for the agent

Counterparty risk transfer for the agent economy: agents post bonds behind their promises, wronged c
Decay-weighted reputation + tamper-evident trust attestations for the agent economy.
Viridis Verified: wrap any MCP server with tamper-evident delivery receipts + metered fees.