A
licenseA
qualityC
maintenanceCryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call. Constraints, chains, AI judgment, invoicing, and local dashboard included.
Last updated
24
22
1
MIT
agent-compute-ledger
Server Details
Compute-is-carbon energy/carbon ledger for agent work with Landauer-limit validation.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jdhart81/viridis-agent-fleet
- GitHub Stars
- 0
- Server Listing
- viridis-agent-fleet
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
B3.3/5.0
Tool DescriptionsC
Average 2.9/5 across 7 of 7 tools scored. Lowest: 2.2/5.
Server CoherenceA
Disambiguation5/5
Each tool targets a distinct operation (record work, list, attest, verify, aggregate, describe) with no overlap. The descriptions clearly differentiate purposes.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (e.g., record_work, verify_chain) or are standalone verbs (attest, footprint). No mixing of conventions.
Tool Count5/5
Seven tools cover the core workflow of a compute ledger (record, list, attest, verify, aggregate, describe) without being excessive or insufficient.
Completeness4/5
The tool set covers the main lifecycle (recording, listing, attesting, verifying, aggregating). A minor gap is the absence of a direct entry retrieval by ID, but list_entries and hash-based verification fill the need.
Available Tools
12 toolsattestInspect
Issue a content-addressed attestation for a ledger entry (verifiable green-compute / energy claim).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entry_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
carbon_receiptInspect
Emit an x402-C carbon receipt for a recorded work entry — the physically-grounded {version, g_co2e, energy_j, method, landauer_*, ...} object an x402 machine-payment receipt can carry. method is 'landauer-floor' when the workload declared bit_ops (thermodynamically validated), else 'measured'. Pass offset_ref (a retirement id from the offset clearinghouse) to assert carbon-neutrality. Read-only; the returned attestation_hash binds the receipt to the ledger's hash chain.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entry_id | Yes | ||
| offset_ref | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
describe_agentInspect
Fleet-standard self-description.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
footprintInspect
Aggregate footprint for an agent: total J, kWh, gCO2e, cost, and mean Landauer efficiency. Totals are exact sums of the ledger entries.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_inventoryInspect
Fetch one immutable inventory record by inventory_id.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| inventory_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_entriesInspect
List all ledger entries for an agent.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_inventoriesInspect
List the separate GHG inventory chain for an agent.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
record_inventoryInspect
Record an audited GHG inventory in a separate append-only chain. mass_g is exact integer grams; content and factor-pack digests are bare lowercase SHA-256 hex. Idempotent on inventory_id.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mass_g | Yes | ||
| agent_id | Yes | ||
| source_ids | No | ||
| inventory_id | Yes | ||
| content_digest | Yes | ||
| factor_pack_digest | Yes | ||
| factor_pack_version | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
record_workInspect
Record a unit of agent compute work. energy_j = power_w * duration_s; carbon_g follows from grid intensity. If bit_ops is declared, the entry is validated against the Landauer floor (bit_ops * kB * T * ln2) — physically impossible claims are rejected. Idempotent on entry_id.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | No | ||
| bit_ops | No | ||
| power_w | Yes | ||
| agent_id | Yes | ||
| entry_id | Yes | ||
| duration_s | Yes | ||
| temperature_k | No | ||
| price_minor_per_kwh | No | ||
| grid_intensity_g_per_kwh | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
verify_attestationInspect
Verify an attestation by recomputing the entry hash.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| attestation | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
verify_chainInspect
Verify the tamper-evident hash chain of an agent's ledger.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
verify_inventory_chainInspect
Verify an agent's inventory hash chain independently of compute work.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityAmaintenanceA causally-ordered, rewindable event-ledger for autonomous AI agents, enabling tamper-evident audit, replay, and rollback of agent actions via an MCP server.Last updated4MIT
- Alicense-qualityCmaintenanceEnables AI coding assistants to estimate their session's energy footprint and retire verified ecocredits on Regen Network, with immutable on-chain proof.Last updated333Apache 2.0
- Alicense-qualityAmaintenanceEnables autonomous agents to calculate deterministic profit and loss, attribute revenue and costs, and generate signed operational reports using x402 micropayments.Last updatedMIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.