Skip to main content
Glama
Sign In
@godman-protocols/lax-mcp

@godman-protocols/lax-mcp

by 195440
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @godman-protocols/lax-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      28 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
      26 npm
      MIT

    • 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
      18 npm
      MIT

    • LAX MCP Server

      mashingaan
      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
      670 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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action: agent search, single offer fetch, job listing, single job fetch, and work submission. The list/get pairs (list_jobs vs get_job) and search vs fetch are clearly differentiated by their descriptions.

    Naming Consistency4/5

    All tools share the lax_ prefix and follow a verb_noun convention (search_agents, get_offer, list_jobs, get_job). Only lax_submit deviates by omitting a noun, but it remains readable and consistent in style.

    Tool Count5/5

    Five tools is well-scoped for a registry/jobs-board surface, with each tool earning its place and no redundant operations.

    Completeness4/5

    Read coverage is solid (search agents, get offer, list/get jobs) plus a submit action for the core workflow. Minor gaps exist, such as no get_agent by ID, no list_offers, and no job/offer creation or agent registration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources