GuardMarket MCP server

GuardMarket — commerce and data skills over MCP

<!-- mcp-name: io.github.zma-petterzhang/guardmarket -->

中文 · 125-skill catalog · Releases · Integration examples

GuardMarket gives MCP clients five tools to discover versioned skills, inspect their schemas and prices, invoke with an explicit spending cap, and read wallet balances and receipts. The catalog describes 125 implemented commerce, inventory, CSV, JSON, text, date, math, statistics, encoding, validation, and unit-conversion skills.

This repository is the public client and documentation. Skill execution, accounts, and billing run in a separately operated GuardMarket backend. Installing this client does not create a backend or a wallet. No public production MCP endpoint, PyPI listing, or official directory approval is claimed. The static website is documentation, not an execution endpoint. The bundled examples are synthetic and contain no account data.

Install and connect

Desktop bundle: download guardmarket-mcp-0.3.0.mcpb from release v0.3.0 and verify it against SHA256SUMS. Open it in a host that supports MCPB 0.4 and its uv runtime. The host manages Python 3.11+; the bundle has no external Python dependencies. Configure your actual backend URL in the install form. Leave the masked consumer API key blank for anonymous discovery. Hosts supporting only older MCPB formats should use the wheel/stdio installation below. This bundle still needs a running backend; it does not install the marketplace server. See bundle details.

Python 3.11+ is required. The Python client has no runtime dependencies.

python3 -m venv .venv
.venv/bin/python -m pip install "git+https://github.com/zma-petterzhang/guardmarket.git@v0.3.0"
.venv/bin/guardmarket-mcp --version

For installation without Git, download the wheel from release v0.3.0, verify its SHA-256 against the release SHA256SUMS, then run python -m pip install /path/to/guardmarket_mcp-0.3.0-py3-none-any.whl. Pin a version or commit in production. On Windows use .venv\Scripts\python.exe and .venv\Scripts\guardmarket-mcp.exe.

Set GUARDMARKET_URL to your backend origin, for example http://127.0.0.1:8787 for a local instance. The client accepts HTTPS origins and numeric-loopback HTTP origins only. Redirects and environment HTTP proxies are disabled.

export GUARDMARKET_URL=http://127.0.0.1:8787
.venv/bin/guardmarket-mcp

The command waits for MCP messages on standard input; it is normally launched by your AI client. market.search and market.describe work anonymously if the backend permits public discovery. The other three tools require a consumer API key created in that backend's account settings. Provide it via the client's environment (GUARDMARKETAPIKEY) or a user-owned mode-0600 regular file (--key-file /absolute/path/key). The key-file option is POSIX-only; environment variables work on Windows. Never put a real key in a committed configuration or a chat message.

Tools and billing behavior

Shortened. The full README is on GitHub.