Skip to main content
Glama
jdhart81

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to viridis-agent-fleet

No user-submitted related servers found.

    Related Servers

    • Agent Guild

      AgentTanuki
      A
      license
      B
      quality
      A
      maintenance
      Agent 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.
      43
      Apache 2.0

    • AI Work Market (AWM)

      darioandyoshi-tech
      F
      license
      Not graded
      quality
      B
      maintenance
      Settlement rails for AI labor — USDC escrow on Base Mainnet, 1% protocol fee, designed for autonomous agents. 10 MCP tools covering the full escrow lifecycle: * Quoting calldata for create-intent, submit-proof, release-funds (broadcast gated) * Single-call x402 payment binding (replaces the 5-step x402 dance with one HMAC-signed POST) * Server-side reputation from on-chain event scan * Li
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources