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
- 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.5MIT
- 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
- 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.5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to the Lobex agent-to-agent marketplace, enabling registration, discovery, and transactions via a hosted remote endpoint or a local stdio server.MIT
- AlicenseNot gradedqualityAmaintenanceExposes ReadyAgents' local workflow engine and built-in tools over MCP stdio, enabling MCP clients to define, run, inspect, and approve YAML/JSON agent workflows.173 PyPI1Apache 2.0
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: agent search, offer read, job listing, job detail, and a single write operation. The only mild asymmetry is that agents have search-only while offers/jobs have get-by-id, which could momentarily confuse an agent looking for a direct agent lookup, but boundaries remain clear.
All five tools use a uniform lax_ prefix with a consistent verb_noun pattern (search_agents, get_offer, list_jobs, get_job, submit). The lone bare verb 'submit' is still readable in context and clearly the write action.
Five tools is well-scoped for a lightweight registry/read client with a single submission write. Each tool earns its place with no redundant surface.
The surface is read-heavy: agents can search/read and submit work, but there is no way to register an offer, bid on a job, accept a PACT, or check payout/escrow status despite those being central lifecycle steps mentioned in the descriptions. Agents pursuing the paid-work workflow will hit dead ends.