aimarket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIMARKET_MCP_KEY | No | Optional bearer token for authentication. Required if AIMARKET_MCP_PRODUCTION is set to 1. | |
| AIMARKET_MCP_PORT | No | Port to listen on (default: 9090). | |
| AIMARKET_MCP_RATE | No | Rate limit per key/IP (default: 120/min). | |
| AIMARKET_METIS_KEY | No | API key for the Metis verification service. | |
| AIMARKET_METIS_URL | No | URL for the Metis verification service (required for metis_verify tool). | |
| AIMARKET_SEARCH_URL | No | URL for the search service (required for web_search tool). | |
| AIMARKET_MCP_PRODUCTION | No | Set to '1' to enable production mode, which requires AIMARKET_MCP_KEY. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_fetch_toolA | Fetch a web page by URL and return its main text content. SSRF-hardened (scheme allow-list, private-IP block, per-redirect re-validation, size cap).
Output is sanitized, role-marker stripped, and wrapped in |
| web_search_toolA | Search the web for current facts and return the top result snippets. Uses DuckDuckGo HTML results. Output is sanitized and wrapped |
| metis_verify_toolA | Run Metis cognition + verification on an input; returns answer plus verify_score/verified. Calls the Metis |
| market_search_toolA | Discover paid AI capabilities listed on an AIMarket hub, with prices. Free — no wallet, key or payment channel. Returns capability_id, product_id, price per call in USD and a trust score; pass both ids to market_invoke to run one. The hub lists only capabilities it can actually execute, so an empty result means it genuinely does not sell that. Set AIMARKET_HUB_URL to point at a different hub. |
| market_invoke_toolA | Run one capability from market_search on the hub's free trial tier. Returns the capability's output plus the nonce of the hub-signed receipt, so the result is verifiable against the hub's published key rather than trusted on faith. A few trial invokes are granted per installation; after that the hub answers 402 and this reports that instead of fabricating a result. Paid access needs an on-chain escrow deposit, which is an operator action and deliberately not available here. |
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 has a fairly distinct purpose: web_search vs web_fetch (find vs retrieve), market_search vs market_invoke (discover vs execute), and metis_verify is a standalone verification endpoint. The only slight overlap is that market_invoke can run arbitrary hub capabilities while metis_verify runs a specific one, which could raise 'which do I call?' questions, but the descriptions clarify the difference.
All five tools follow the same {domain}_{verb}_tool snake_case convention (web_search_tool, market_invoke_tool, market_search_tool, metis_verify_tool, web_fetch_tool). The redundant '_tool' suffix is unnecessary but applied uniformly, so it remains fully predictable.
Five tools is a lean but reasonable set covering search, fetch, market discovery, invocation, and verification. It is on the thin side for a market/hub server since no tool exposes trial quota, hub config, or errors-as-state beyond what invoke returns, but nothing feels padded.
The core loop is covered: discover capabilities (market_search), run one (market_invoke), verify output (metis_verify), plus web search/fetch for grounding. Minor gaps exist (no tool to inspect remaining trial invokes or hub status), and paid escrow is intentionally excluded, but agents can work around these.