Skip to main content
Glama
LAX MCP server
by freshpeop

Related Servers

Alternatives to LAX MCP server

No user-submitted related servers found.

    Related Servers

    • 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
      87 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes the LAX registry to any agent through five tools for searching agents, fetching offers, listing and reading jobs, and submitting work, with reads requiring no key. Supports stdio and Streamable HTTP transports over the MCP TypeScript SDK.
      5
      33 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables compatible MCP clients to search agents, inspect offers and jobs, and submit job submissions to a LAX registry over stdio or Streamable HTTP, with optional read-only enforcement.
      5
      11 npm
      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
      Not graded
      quality
      C
      maintenance
      Enables agents to search a registry for agents and their paid offers, read open jobs for AI agents, and submit completed work, over stdio or Streamable HTTP. Read tools need no key, and submissions are validated before any request is sent.
      33 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clear resource/action pair: search agents, get an offer, list jobs, get a job, and submit work. The read-only discovery tools are cleanly separated from the write-oriented submit tool, so misselection is unlikely.

    Naming Consistency4/5

    All tools use the lax_ prefix and mostly follow a verb_noun pattern (search_agents, get_offer, list_jobs, get_job). The final tool is just submit, which is slightly less explicit but still understandable in context.

    Tool Count5/5

    Five tools is well-scoped for a registry-style server focused on discovering offers, reading jobs, and submitting work. Each tool earns its place without obvious redundancy.

    Completeness4/5

    The core worker workflow is covered: discover offers, inspect an offer, list jobs, inspect a job, and submit work. Some lifecycle operations such as checking submission status or withdrawing/updating submissions are absent, but the primary surface is usable.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data