uex-market-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UEX_TOKEN | No | Optional UEX token, for a quota of your own. | |
| UEX_MARKET_CACHE | No | Catalog cache directory. | ~/.cache/uex-market |
| UEX_MCP_OAUTH_SHIM | No | Set to 1 to enable an auto-approving OAuth facade. | off |
| UEX_MCP_PUBLIC_URL | No | Public base URL, required by the OAuth facade. | |
| UEX_MAX_CALLS_PER_MIN | No | Outgoing UEX traffic capped per process (calls per minute). | 40 |
| UEX_MCP_ALLOWED_HOSTS | No | Public host names accepted (DNS rebinding protection). | |
| UEX_MCP_OAUTH_REDIRECT_HOSTS | No | Redirect hosts accepted by the OAuth facade. | claude.ai,claude.com,localhost,127.0.0.1 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Find player listings on the UEX marketplace with combined filters (item, quality range, age, price, system, location, seller, title words, category), ranked by quality, recency or price. Each result has a direct link to the listing. |
| find_itemsA | Look up items in the UEX catalog by name (typo tolerant) to get their exact names and ids before searching listings. |
| marketplace_statusB | Freshness of the catalog and caches, and the UEX call budget. |
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 3 tools
Each tool has a clearly distinct role: find_items resolves catalog items, search_listings queries marketplace listings, and marketplace_status reports cache freshness/budget. There is no practical overlap that would cause misselection.
All names use snake_case, and search_listings/find_items follow a clear verb_noun pattern. marketplace_status deviates slightly as a noun phrase, but the set remains readable and predictable.
Three tools is modest but appropriate for a focused, read-only marketplace search server. Each tool serves a clear purpose, though the surface is on the minimal side.
The set covers item lookup, listing search, and cache status, but lacks direct retrieval of listing details by ID or deeper item details. Relying on external links for listing details is a notable gap for an agent-driven workflow.