Aimarket MCP

What alexar76/aimarket-mcp MCP server does

The gateway combines general web tools with AIMarket discovery and invocation. Its five tools are web_fetch, web_search, metis_verify, market_search, and market_invoke.

web_fetch retrieves a URL and returns its primary text using a lightweight readability step. Requests are SSRF-guarded, and the resulting content is sanitized and wrapped as untrusted data. web_search performs live DuckDuckGo searches and returns top snippets with similar output sanitization. These safeguards help agents use external content without treating fetched text as trusted instructions.

metis_verify sends cognition and verification work through the configured Metis service. Its result includes an answer together with a verification score and a boolean verification gate. The two market tools query an AIMarket hub for priced capabilities and run a selected capability through the hub's free trial tier. Trial invocation returns a signed receipt nonce; once the allowance is exhausted, the hub's HTTP 402 response is reported.

How it works

The server is implemented in Python with the official MCP SDK and FastMCP. A stdio entrypoint is provided for local MCP hosts such as Claude Desktop and Cursor. A separate HTTP entrypoint listens on port 9090 by default and exposes the MCP endpoint for self-hosted deployments.

The web tools use configured service endpoints, while the market tools use the AIMarket hub specified by AIMARKET_HUB_URL. The default hub is https://modelmarket.dev. A sandbox visitor identity can be supplied to preserve a market trial allowance across reinstalls. External-wallet settlement is outside the documented trial path and requires a separate escrow flow.

Setup and configuration

Install the published package with uvx aimarket-mcp or configure that command as the stdio process in an MCP client. A source checkout can instead be installed with pip install -e . and started with python -m aimarket_mcp.stdio_server.

The HTTP process is started with the aimarket-mcp-http console script, or through Docker Compose. In production mode, setting AIMARKET_MCP_PRODUCTION=1 makes AIMARKET_MCP_KEY mandatory for bearer authentication. AIMARKET_MCP_RATE controls the request limit per key or IP, and AIMARKET_MCP_PORT changes the listening port.

alexar76/aimarket-mcp MCP server also accepts AIMARKET_METIS_URL and the optional AIMARKET_METIS_KEY for Metis, AIMARKET_SEARCH_URL for a DuckDuckGo endpoint override, and AIMARKET_SANDBOX_VISITOR for trial identity persistence.

Tools and capabilities

• Fetch main text from URLs with SSRF checks and sanitized output.
• Search DuckDuckGo and return top result snippets.
• Request Metis verification results with score and gate fields.
• Discover capabilities listed by an AIMarket hub.
• Invoke one discovered capability through its free trial allowance.
• Run through stdio or Streamable HTTP.

Limitations and notes

The repository is a read-only mirror of a canonical monorepo, so changes should be proposed through the linked issue process rather than by relying on direct repository edits. market_search and market_invoke only expose capabilities that the selected hub can execute. The market trial requires neither a wallet nor an API key, but it is limited per caller and may return HTTP 402 after the allowance is consumed.

HTTP production authentication is optional only when production mode is disabled. The Metis bearer key is also optional according to the configuration table. The package does not replace the separate on-chain escrow process required to prove an externally funded wallet payment.