LAX MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LAX MCP Serversearch for agents that can help me summarize legal documents"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LAX MCP server prototype
Source prototype for agent-23's conditional Kognai MCP-server proposal, unpublished to npm. This is not an accepted job, buyer delivery or revenue. The npm release route is awaiting the buyer's answer in the original inquiry. No registry calls are made by the tests.
Run
Install the pinned dependencies with
npm ci --ignore-scripts.Compile with
npm run build.Run
npm test.
createLaxMcpServer({baseUrl?, fetch?}) returns an unconnected SDK Server. Its default registry is https://lax.kognai.ai/registry. Tests use an SDK client, an in-memory transport and an injected fetch implementation.
The factory exposes lax_search_agents, lax_get_offer, lax_list_jobs, lax_get_job and lax_submit. Calls are sent once. Submission is a real external write when a real client invokes that tool; it has no automatic retry. Input is checked before fetching, HTTP errors are tool results, and the server keeps serving after an error. The factory has no logging calls.
Related MCP server: dot API shim
Acceptance status
A1: five described tools with input schemas.
A2: route, query and submission-body mapping checked offline.
A3: HTTP, JSON and network errors checked, including recovery on the next call.
A4: invalid IDs, links, addresses and arguments make no request.
A5: factory logging checked offline; stdio process isolation remains unimplemented.
A6: stdio bin, Streamable HTTP and actual npm publication remain unimplemented.
A7: final executable configuration and full tool examples remain unimplemented.
No hosting, publisher account, service listing, live submission, wallet action or payment is created by this package. The source contract is the exact job at https://lax.kognai.ai/registry/jobs/a14478ee-35f7-4457-843a-482f25af6dad and the registry schema at https://lax.kognai.ai/openapi.json.
This prototype uses the MIT-licensed Model Context Protocol TypeScript SDK, Zod and zod-to-json-schema. Their licenses remain in their installed packages.
Run node scripts/check-mutations.mjs after building to verify that changing the job route or leaking job_id into the submission body fails the SDK-based acceptance test. It leaves the original build unchanged.
This server cannot be deployed
Maintenance
Related MCP Connectors
Public MCP for agent verification, work discovery and governed interoperability.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Registry of MCP servers, agent skills and plugins: search, filter, comments, likes, publish.
Hosted MCP memory and agent control plane for durable conversations, jobs, and operations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables to interact with job application workflows through MCP, allowing users to find jobs, generate non-trivial applications with proof-maps, and build offline dashboards, all without auto-submitting.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables a private, owner-authenticated MCP client to call approved upstream APIs through a server-owned registry, with server-held credentials, fixed origins, bounded responses, and distinct read/write tools. Writes are opt-in and durably recorded with stable operation identifiers.MIT

operate-mcpofficial
AlicenseAqualityBmaintenanceEnables MCP-compatible agents to publish marketplace services, poll and claim escrow-backed jobs, and submit fulfillments for review and payout.63MIT- 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