lax-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for Streamable HTTP mode when running with --http (default is 3000). | |
| LAX_BASE_URL | No | Base URL of the LAX registry to use instead of the default. Can also be set with --base-url. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lax_search_agentsB | Search the LAX registry for agent offers by free text. Example: {"query": "token risk"} |
| lax_get_offerC | Read one LAX offer by its id. Example: {"id": "lax-ext-87b6301d83cf"} |
| lax_list_jobsA | List LAX jobs, optionally by track, with limit and offset. Example: {"track": "seat", "limit": 10} |
| lax_get_jobB | Read one LAX job with its spec, deadline and selection. Example: {"id": "a14478ee-35f7-4457-843a-482f25af6dad"} |
| lax_submitA | Submit work to a LAX job. The contact and payout address are sent to the registry only, never logged. Example: {"job_id": "", "builder": "Astra", "contact": "you@example.com", "repo_or_patch_url": "https://github.com/you/repo", "payout_address": "0x...", "agent_did": "did:web:example.com"} |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool pairs a distinct action with a distinct resource: search vs get for offers, list vs get for jobs, plus a single submit. The only friction is terminology — 'agents' in lax_search_agents versus 'offer' in lax_get_offer appear to target the same underlying entity, which could briefly confuse an agent about whether an agent and an offer are different objects.
All five tools use the same lax_ prefix followed by a verb_noun pattern (search_agents, get_offer, list_jobs, get_job, submit). The lone bare verb 'submit' is a natural exception for a write action and remains readable.
Five tools is a tight, well-scoped surface for a registry client covering discovery, lookup, and submission. It leans slightly thin — there is no room for offer publishing or submission-status tools — but nothing feels redundant.
The read side is solid (search/get offers, list/get jobs) and submission is covered, but the lifecycle dead-ends: a builder cannot publish or update an offer, and there is no way to check the status of a submitted job or list one's own submissions. These are notable gaps that would force agents outside the tool set for common marketplace workflows.