🔄 Synced from a monorepo — but with a live history.
aimarket-mcpmirrors the canonical AI-Factory monorepo. History here is append-only (no force-push). Pull requests are welcome — merged PRs are imported back into the monorepo and re-synced here, so your contribution becomes canonical. 💬 Issues · Pull requests both welcome.
aimarket-mcp — ecosystem MCP gateway
🟢 Just want to try the marketplace? Install nothing.
Paste
https://modelmarket.dev/mcpinto your MCP client and you havemarket_searchandmarket_invokeagainst the live hub, with a few free trial invokes per caller and a signed receipt for each — no wallet, no key, no install. →docs/hosted-mcp-endpoint.mdInstall this package when you want the other three tools (
web_fetch,web_search,metis_verify), or want to point the market tools at a hub of your own.
One MCP gateway. Five hardened tools. Shared by Metis, ARGUS, and the ecosystem.
Transport: stdio (aimarket_mcp/stdio_server.py) for Glama / Claude Desktop / Cursor, built with the
official Model Context Protocol Python SDK (mcp, FastMCP).
Also ships Streamable-HTTP on :9090 for self-hosted deployments (aimarket-mcp-http, Docker Compose).
Compatible hosts: Claude Desktop, Cursor, Glama, and any MCP client that supports stdio or Streamable-HTTP.
Tools
Example — buy a GAIA Open-Meteo reading
market_search_tool(intent="gaia weather open-meteo")
market_invoke_tool(
capability_id="gaia.weather.read@v1",
product_id="gaia.gateway",
source_hub="https://iot.modelmarket.dev",
# input JSON with device_id om-wx-01 — see tool schema / hub docs
)
Or the same HTTP the tool wraps:
curl -s -X POST "${AIMARKET_HUB_URL:-https://modelmarket.dev}/ai-market/v2/invoke" \
-H 'Content-Type: application/json' \
-H 'X-AIMarket-Sandbox-Visitor: vis_mcp_om_wx' \
-d '{"capability_id":"gaia.weather.read@v1","product_id":"gaia.gateway",
"source_hub":"https://iot.modelmarket.dev","input":{"device_id":"om-wx-01"}}'
That is the easy path (trial/sandbox). Proving an external wallet paid on-chain
is a separate escrow flow (openChannel → DebitAuthorization → hub debit/settle) —
see docs/onchain-journal.md §3l–§3m and
gaia/docs/LIVE-RELAYS.md.
Why a gateway (not per-agent tools): generic capabilities are written once; the security core lives in one audited place. Ecosystem-specific capabilities live in their own MCP servers (aimarket-oracle-gateway, aimarket-plugins).
Configure (env)
Run (stdio — Glama / Claude Desktop)
Claude Desktop (mcpServers entry) — no clone, no working directory to get wrong:
{
"mcpServers": {
"aimarket-mcp": {
"command": "uvx",
"args": ["aimarket-mcp"]
}
}
}
uvx fetches the published package and runs its aimarket-mcp console script, which is
the stdio server. With the package already installed, "command": "aimarket-mcp" and no
args does the same thing.
From a checkout, for development:
pip install -e .
python -m aimarket_mcp.stdio_server
Run (HTTP — self-host)
pip install -e .
AIMARKET_MCP_KEY=sk-... AIMARKET_MCP_PRODUCTION=1 aimarket-mcp-http # :9090
# or: docker compose up -d (uses Dockerfile.http)
Cursor / Claude (Streamable HTTP)
{
"mcpServers": {
"aimarket-web": {
"type": "streamable-http",
"url": "http://127.0.0.1:9090/mcp",
"headers": {
"Authorization": "Bearer YOUR_AIMARKET_MCP_KEY"
}
}
}
}
Publish on Glama
Listing: aimarket-mcp. Glama generates a container from the build settings in its admin panel:
Build, inspect, and publish a release after syncing source changes. A repository sync alone does not refresh the deployed tool catalog or its quality evaluation. The catalog should contain all six tools listed above. See Glama build and release instructions.
Consumers
- Connected successfully? Share your host, configuration, and one working tool using the Show and tell template.
- Metis — enable the preset:
enable_mcp_tools: true mcp_ecosystem_presets: [aimarket-web] - ARGUS — add the server to
argus.config.jsonmcpServers(see that repo).
Test
pip install -e '.[dev]' && pytest -q
Registries
See the directory submission checklist and current status before submitting or refreshing a listing.