Skip to main content
Glama
README.md
# Viridis Agent Fleet: open-source agents for the agent economy

Deterministic, auditable MCP agents: trust and settlement rails (identity, trust, escrow, metering, arbitration, notary, surety, provenance, covenant, offsets, compute-ledger) and priced-grade services (tax credits, GHG accounting, construction takeoff, measurement, compliance). Every core is pure Python with no LLM in the serving path, and every result is content-addressed so anyone can re-verify it.

**Licensed Apache-2.0.** Run any agent yourself, fork it, embed it.

## Run an agent locally (free, forever)
```bash
pip install -r requirements-dev.txt
python3 agent-escrow-agent/adapters/mcp_server.py          # stdio MCP
python3 run_fleet_tests.py                                 # every agent's invariant tests
```

## Or use the hosted fleet
`https://mcp.viridisconservation.com` runs all agents as one managed MCP service:

| | Self-hosted (this repo) | Hosted by Viridis |
|---|---|---|
| Agent logic & verification | ✅ identical | ✅ identical |
| Viridis-signed receipts & notary chain | – | ✅ |
| Shared trust/reputation network data | – | ✅ |
| Maintained rule packs (tax, GHG factors, regs) | snapshot | ✅ kept current |
| Payments (x402, card), seats, SLA | – | ✅ |

Free tier: 10 calls/day per service; the rails (identity, escrow, metering…) are free forever. Verification is always free.

## Boundary
This repo contains agent cores, MCP adapters, tests, standards and self-host tooling. The hosted service layer (gateway, payment and settlement, seats, signing authority, operations, telemetry and customer data) is proprietary and is not in this repo. Please don't open PRs that add it.

"Viridis", "Viridis Conservation" and the Viridis marks are trademarks of Viridis LLC; see `TRADEMARKS.md`.

TDQS

C2.7/5.0

Scored across 220 tools

Disambiguation3/5

Within each namespaced sub-agent (e.g., escrow__*, metering__*), tools are reasonably distinct. However, across the fleet there is heavy conceptual overlap: offsets, ghg-ledger, compute-ledger, and green-router all offer carbon accounting/verification tools; trust, erc8004, provenance, and identity all cover reputation/identity; escrow, surety, metering, subscriptions, and hive all touch settlement. The detailed descriptions help, but an agent can easily misselect among these overlapping domains.

Naming Consistency4/5

Almost all tools follow a consistent server__snake_case pattern, with predictable verb_noun or noun phrases (list_projects, verify_certificate, carbon_receipt). Minor deviations exist: some sub-agents expose describe_agent while others use describe or health, and hyphens appear in namespace prefixes. Overall highly readable and consistent.

Tool Count1/5

220 tools is far beyond any reasonable single-server surface, even for a fleet. The rubric flags 50+ tools as an extreme mismatch, and this is more than four times that threshold. The enormous count makes discovery, selection, and maintenance impractical without heavy namespace filtering.

Completeness4/5

Across the many sub-domains (carbon offsets, escrow, metering, identity, trust, provenance, compliance, etc.) coverage is deep, with create/read/update/verify/lifecycle operations present. Some cross-fleet gaps may exist (e.g., no unified cross-domain audit), but each sub-agent appears largely complete for its stated purpose.

Maintenance

ActivityActive
ResponsivenessUnresponsive