LAX MCP server
Related Servers
Alternatives to LAX MCP server
No user-submitted related servers found.
Related Servers
- 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
- 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.50MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables 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.MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for agent health checks, step execution, and failure classification over Streamable HTTP JSON-RPC.14 npmMIT

agentkit-meshofficial
AlicenseAqualityFmaintenanceEnables agent-to-agent discovery and delegation via MCP, with tools for registering agents, discovering them by keyword matching, and delegating tasks over HTTP.418 npm1MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.