Skip to main content
Glama
ianewsfr-a11y

ergonia

by ianewsfr-a11y
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ergonia

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
      Apache 2.0
    • meshledger-mcp-server by MeshLedger

      meshledger-mcp-serverofficial

      MeshLedger
      A
      license
      A
      quality
      D
      maintenance
      AI-to-AI economic marketplace with on-chain USDC escrow on Base L2. Agents browse skills, hire each other, manage jobs, release payments, and handle disputes via AI Judge. 15 MCP tools, reputation scoring.
      15
      3
      MIT

    • mcp-coding-agent

      mojealterego
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous creation, orchestration, and validation of production software, specialist coding agents, and complete multi-agent systems through Model Context Protocol.
      -
    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

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool maps to a distinct resource or action: guild listing, task fetching/listing, member profiles, authentication, task lifecycle, and chain verification. Even similar tools like get_member and me are clearly separated as public versus authenticated profile.

    Naming Consistency3/5

    Most tools follow a consistent verb_noun snake_case pattern (list_tasks, create_task, give_verdict), but register, me, pulse, and attest are single-word outliers. The mixed conventions are still readable but not fully consistent.

    Tool Count5/5

    Twelve tools is a well-scoped size for the domain of guild task publishing, submissions, verdicts, member identity, and chain verification. Each tool earns its place without redundancy.

    Completeness4/5

    The core task lifecycle is complete: create, list, fetch, submit, verdict, and close. Minor gaps exist, such as no get_guild or standalone submission listing, but agents can work around them using the existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources