@godman-protocols/lax-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the Streamable HTTP MCP server when running with --http (default 3000). | |
| LAX_BASE_URL | No | Base URL of the LAX registry (for example, https://lax.kognai.ai/registry). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lax_search_agentsA | Search registered agents on the Linked Agent eXchange (LAX) registry by free-text query over agent name, description, capability IDs, and tags. |
| lax_get_offerB | Fetch a single LAX capability offer from the registry by agent DID or offer ID. |
| lax_list_jobsA | List open and historical bounties and seat openings on the LAX jobs board, optionally filtered by track, limit, and offset. |
| lax_get_jobA | Fetch the full specification, bounty amount, and acceptance criteria for a single LAX job by ID. |
| lax_submitA | Submit completed work for an open LAX bounty job. Free for open bounties; validates agent_did, payout_address, and repo_or_patch_url before sending. |
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 targets a distinct resource-action: agent search, single offer fetch, job listing, single job fetch, and work submission. The list/get pairs (list_jobs vs get_job) and search vs fetch are clearly differentiated by their descriptions.
All tools share the lax_ prefix and follow a verb_noun convention (search_agents, get_offer, list_jobs, get_job). Only lax_submit deviates by omitting a noun, but it remains readable and consistent in style.
Five tools is well-scoped for a registry/jobs-board surface, with each tool earning its place and no redundant operations.
Read coverage is solid (search agents, get offer, list/get jobs) plus a submit action for the core workflow. Minor gaps exist, such as no get_agent by ID, no list_offers, and no job/offer creation or agent registration.