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
      B
      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
      1
      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
      -

    • moltbridge

      SageMindAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Agent network intelligence for trust verification, broker discovery, and capability matching. Ed25519 identity, graph-based trust scoring, USDC payments, and MCP tools for agent registration, search, and trust attestation.
      771 npm
      5
      MIT
    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.8/5.0

    Scored across 205 tools

    Disambiguation4/5

    The namespace prefix on every tool makes repeated generic verbs like verify_* and describe_agent mostly unambiguous, and within each namespace the tools address clearly distinct resources/actions. A few near-homophones, such as offsets__list_credit versus offsets__book, and buy_offset versus buy_offset_budget, could cause minor misselection, but the descriptions clarify the boundaries.

    Naming Consistency4/5

    The dominant namespace__verb_noun snake_case pattern is strong and predictable across the entire fleet. Minor deviations exist: smartscale__describe and protogen__describe lack the _agent suffix, a few read-only tools use bare nouns like offsets__book and offsets__net_position, and viridisos redundantly repeats viridis_ in tool names.

    Tool Count1/5

    205 tools is an extreme count for any MCP server. Even though the server is explicitly an agent fleet, exposing this many tools in one flat surfaces creates a massive selection burden and should be split into per-namespace servers or wrapped behind a discovery layer.

    Completeness4/5

    Most namespaces have strong lifecycle coverage: escrow, surety, covenant, metering, provenance, identity, neurogenesis, offsets, and compute-ledger all provide create/get/list/verify or equivalent flows. The gaps are minor but real, such as wavefunction exposing only describe_agent with no actual discovery action and viridisos lacking a list/get certificate endpoint.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources