Skip to main content
Glama
Sign In
lax-mcp-server

lax-mcp-server

by astra-tc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to lax-mcp-server

No user-submitted related servers found.

    Related Servers

    • LAX MCP server

      Trex2021
      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
      41 npm
      MIT

    • lax-mcp-server

      landingen24h
      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
      24 npm
      MIT

    • LAX MCP server

      freshpeop
      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
      337 npm
      MIT

    • lax-mcp-server

      nathanielc3d
      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.
      24 npm
      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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool pairs a distinct action with a distinct resource: search vs get for offers, list vs get for jobs, plus a single submit. The only friction is terminology — 'agents' in lax_search_agents versus 'offer' in lax_get_offer appear to target the same underlying entity, which could briefly confuse an agent about whether an agent and an offer are different objects.

    Naming Consistency5/5

    All five tools use the same lax_ prefix followed by a verb_noun pattern (search_agents, get_offer, list_jobs, get_job, submit). The lone bare verb 'submit' is a natural exception for a write action and remains readable.

    Tool Count4/5

    Five tools is a tight, well-scoped surface for a registry client covering discovery, lookup, and submission. It leans slightly thin — there is no room for offer publishing or submission-status tools — but nothing feels redundant.

    Completeness3/5

    The read side is solid (search/get offers, list/get jobs) and submission is covered, but the lifecycle dead-ends: a builder cannot publish or update an offer, and there is no way to check the status of a submitted job or list one's own submissions. These are notable gaps that would force agents outside the tool set for common marketplace workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources