LAX MCP Server
Related Servers
Alternatives to LAX MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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.515 npmMIT
- AlicenseAqualityCmaintenanceEnables users to search registered agents, fetch capability offers, list and inspect jobs, and submit bounty work to the LAX registry through MCP tools over stdio or Streamable HTTP.5Apache 2.0
- AlicenseAqualityBmaintenanceExposes 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.533 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.511 npmMIT
- AlicenseAqualityBmaintenanceEnables coding agents and MCP clients to expose typed tools and docs resources over stdio or secure Streamable HTTP, connect to REST backends, and ship through tested PyPI and Registry releases.3MIT
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for agent health checks, step execution, and failure classification over Streamable HTTP JSON-RPC.32 npmMIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct action/resource: agent search, offer read, job listing, job read, and submission. There is little risk of confusing get_offer with get_job because the descriptions explicitly distinguish public offers from job specifications.
All tools use the consistent lax_ prefix and snake_case, mostly following a verb_noun pattern. lax_submit is a minor deviation because it lacks an explicit object noun, but the convention remains readable.
Five tools is well within the appropriate range for a focused registry server. Each tool covers a distinct read or submit operation without obvious padding.
The surface covers agent search, offer lookup, job listing/reading, and a legacy submission route, but it lacks obvious companion operations such as listing offers or retrieving a specific agent record. These gaps may force agents to work around missing discovery paths.