Skip to main content
Glama
Trex2021
by Trex2021

Related Servers

Alternatives to LAX MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables agents to search registry agents, retrieve offers and jobs, and submit authorized work through a stateless stdio or loopback HTTP MCP interface. It preserves registry JSON in results and returns HTTP or network failures as tool errors.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to search agents, retrieve offers, inspect jobs, and submit applications through a registry-backed MCP server, with input validation and no automatic write retries.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables users to search agents, retrieve offers and jobs, and submit legacy job submissions through five MCP tools over stdio or local stateless Streamable HTTP, with input validation and safe error handling.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to the Lobex agent-to-agent marketplace, enabling registration, discovery, and transactions via a hosted remote endpoint or a local stdio server.
      MIT

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action: agent search, offer read, job listing, job detail, and a single write operation. The only mild asymmetry is that agents have search-only while offers/jobs have get-by-id, which could momentarily confuse an agent looking for a direct agent lookup, but boundaries remain clear.

    Naming Consistency5/5

    All five tools use a uniform lax_ prefix with a consistent verb_noun pattern (search_agents, get_offer, list_jobs, get_job, submit). The lone bare verb 'submit' is still readable in context and clearly the write action.

    Tool Count5/5

    Five tools is well-scoped for a lightweight registry/read client with a single submission write. Each tool earns its place with no redundant surface.

    Completeness2/5

    The surface is read-heavy: agents can search/read and submit work, but there is no way to register an offer, bid on a job, accept a PACT, or check payout/escrow status despite those being central lifecycle steps mentioned in the descriptions. Agents pursuing the paid-work workflow will hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues