Hogswap MCP

What hogswap-mcp does

The hogswap-mcp MCP server exposes HOGSWAP capabilities to AI agents working with Algorand assets. It can find DEX-aggregated swap quotes, produce unsigned transaction groups, and pay Algorand-settled x402 invoices using between one and four assets held by the user. Invoice payment uses an exact-out route so the requested payment amount is funded by the resulting swap.

This belongs in the Finance & Fintech category for workflows where an agent needs to prepare transactions but must not control funds. The server is explicitly non-custodial: signing and blockchain submission remain outside the server and are handled by the wallet tooling chosen by the user.

How it works

The hogswap-mcp MCP server can be started as a local Node process using stdio, or accessed without a local process through HOGSWAP’s Streamable HTTP MCP endpoint. Local mode sends requests to the configured HOGSWAP API. Remote clients connect to the documented /mcp/ URL and provide an API key as a bearer token when authentication is needed.

A typical payment flow starts with an invoice and produces two transaction groups: one for the asset swap and one for the invoice payment. The caller signs every transaction, submits the swap first, and then submits the payment group. The swap’s on-chain floor is intended to ensure that the payment has sufficient funding.

Agents can obtain a key through the registration flow: call register_agent, complete the required signing step, and send the result to verify_registration. API-key-protected tools reject unauthenticated requests rather than creating a transaction build.

Setup and configuration

Install the Node dependencies, then start the entry point with Node. A key can be supplied through HOGSWAP_API_KEY; it is optional for the free tools and required for protected operations. HOGSWAP_API_URL changes the API base URL from its default HOGSWAP endpoint, which is useful when targeting another instance.

For remote use, connect an MCP client to the trailing-slash URL https://hogswap-v1.liquihog.dev/mcp/. The bare /mcp path redirects, adding an avoidable request. Send the HOGSWAP key in an Authorization: Bearer header.

Never provide the server with a mnemonic or private key. Smoke tests support read-only and build-only checks; they do not sign or broadcast transactions.

Tools and capabilities

The hogswap-mcp MCP server includes free tools for listing payable assets, requesting quotes, and registering or verifying an agent. Quote requests accept an optional max_legs value from 1 through 16, allowing callers to limit route complexity and included splits.

Key-protected capabilities include swap building, x402 invoice payment, credit offers, balance lookup, and price or target watches. Watch management includes creating, listing, and deleting watches. From MCP, callers poll list_watches; the service can also emit watch events through its SSE stream. Watch events provide numeric hints only, so callers should request a fresh quote before acting.

Limitations and notes

Transaction-producing operations return unsigned groups only. The server does not sign or submit them. Invoice payment requires the groups to be processed in order, and watch alerts do not replace a current quote. Credit top-ups use an x402 invoice as well; its first accepted payment option and associated note value can be passed to the invoice-payment flow.

Getting started with this hogswap-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.