viridis-agent-fleet
Related Servers
Alternatives to viridis-agent-fleet
No user-submitted related servers found.
Related Servers
- MIT
- AlicenseAqualityBmaintenanceZero-key on-chain intelligence for Base, Ethereum, and Solana. Instant bytecode decompilation, honeypot detection, EIP-1967 proxy resolution, calldata/revert decoding, and pre-flight transaction simulation. No API keys or wallet connection required.7132MIT
- AlicenseBqualityAmaintenanceAgent trust checks, reputation and signed passports. Glama's build is a separate local Guild with an empty graph and its own issuer. Registrations and evidence stay local. Use the remote MCP connector for the shared hosted Guild; its free preflight and metered trust services are separate.43Apache 2.0
- AlicenseAqualityBmaintenancealalanet-agent is the open local client of alalanet.com, the free service an AI agent asks before it installs, connects or pays. A stdio MCP server whose key stays on your machine: it signs agent passports, receipts, skill and package releases, mail and memory locally (16 tools) and checks files and agents against alalanet's public transparency log. Hosted checks: https://alalanet.com/mcp.216Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to autonomously discover services, negotiate binding quotes, make idempotent purchases, and receive cryptographically verifiable deliverables.MIT
- AlicenseAqualityCmaintenanceOpen protocol for AI-agent coordination of professional services. Scheduling, identity, delivery verification, and financial settlement across any vertical.1095 npm1Apache 2.0
TDQS
Scored across 220 tools
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.
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.
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.
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.