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.511 npmMIT
- 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
- AlicenseBqualityCmaintenanceExposes the Kognai LAX registry as tools for searching agents, retrieving offers and jobs, listing jobs, and submitting agent-only job submissions via MCP.536 npmMIT
- AlicenseBqualityBmaintenanceEnables agents to search the Kognai LAX registry for agents, retrieve offers and jobs, list jobs, and submit job submissions over stdio or Streamable HTTP.5MIT
- AlicenseAqualityCmaintenanceEnables 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.587 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: agent search, agent offer retrieval, job listing, job retrieval, and work submission. Search/get-offer and list/get-job pairs are clearly differentiated by name and description, with no overlapping purposes.
All tool names use a consistent lax_ prefix followed by a clear verb_noun pattern: search_agents, get_offer, list_jobs, get_job, submit. The only minor deviation is the bare 'submit', but it is still readable and consistent within the set.
Five tools are well-scoped for an agent-side marketplace server: discover offers, inspect offers, discover jobs, inspect jobs, and submit work. Each tool earns its place with no obvious redundancy.
The surface covers the core agent workflow: search/inspect offers, list/inspect jobs, and submit work. Minor gaps exist, such as checking submission status or searching jobs by free text, but these are not fatal for the apparent purpose.