Sealed-bid RFQs, HTLC atomic settlement, and a Model Context Protocol server that lets Claude trade for you.
Trading crypto OTC has always been a trust problem. You find a counterparty on Telegram, negotiate a price, and hope nobody front-runs or ghosts. Institutions do it over Bloomberg chat. Retail does it on DEXs and eats slippage.
We built Hashlock Markets to fix both sides — and then we gave AI agents the keys.
What is Hashlock Markets?
Hashlock Markets (hashlock.markets) is an intent-based trading protocol for swapping any asset — crypto, RWAs, and stablecoins — with private sealed bids and verified counterparties.
Here's how it works:
- You declare an intent — "I want to sell 10 ETH for USDC, minimum price $3,200."
- Market makers respond with sealed bids — nobody sees anyone else's price.
- Best bid wins — transparent settlement via Hash Time-Locked Contracts (HTLCs).
- Atomic settlement — both sides of the trade execute simultaneously, or neither does. No escrow. No trust.
The result: zero slippage, no front-running, and no information leakage before execution.
A note on the name: "Hashlock" refers to our trading platform and brand — Hashlock Markets, built by Hashlock-Tech. We are not affiliated with Hashlock Pty Ltd (hashlock.com), the Australian smart contract auditing firm. Our protocol uses the cryptographic hash-lock primitive (as in HTLCs), but "Hashlock" as a product name refers to this trading platform specifically.
Why AI Agents?
Here's the thing about intent-based trading: it's perfectly suited for AI agents.
An intent is just structured data — asset pair, amount, direction, constraints. There's no chart to read, no order book to stare at. You express what you want, and the protocol finds the best execution.
This is exactly how LLMs think. They're great at understanding natural language ("swap 5 ETH for USDC, best price, settle on Ethereum") and terrible at pixel-level chart analysis. Intent trading plays to their strengths.
So we built an MCP server.
The Hashlock MCP Server
The Hashlock MCP server implements the Model Context Protocol — the open standard that lets AI assistants like Claude, GPT, and others interact with external tools.
Five Core Tools
The server exposes five tools that cover the full trading lifecycle:
create_intent — Create a new trading intent with asset pair, amount, direction, and price constraints. Supports ETH, BTC, SUI, USDC, USDT, and any ERC-20.
validate_intent — Check an intent for correctness before submission. Catches issues like insufficient balance, invalid pairs, or malformed parameters.
commit_intent — Lock an intent on-chain, triggering the sealed-bid RFQ process. Market makers see the intent but not each other's bids.
explain_intent — Get a human-readable breakdown of what an intent will do, including estimated fees, settlement chain, and time-lock parameters.
parse_natural_language — Convert plain English into a structured intent. "Sell 2 BTC for USDC on Ethereum, minimum $68k" becomes a valid intent object.
Two Ways to Connect
stdio (local) — Install via npm and run locally:
npx -y @hashlock-tech/mcp
Streamable HTTP (remote) — Connect directly to our hosted endpoint:
https://hashlock.markets/mcp
Both require a SIWE (Sign-In with Ethereum) bearer token for authentication. You sign once with your wallet at hashlock.markets/sign/login, and the token is valid for 30 days.
Cross-Chain by Default
Hashlock Markets supports settlement on Ethereum, Bitcoin, and Sui — with more chains coming. The HTLC mechanism is chain-agnostic: as long as both chains support hash verification and time locks, atomic settlement works.
This means an AI agent can execute a trade like "swap 1 BTC on Bitcoin mainnet for 20 ETH on Ethereum" — and both legs settle atomically. No bridge. No wrapped tokens. No custodian.
For Market Makers
If you're running a trading desk or market-making operation, Hashlock Markets gives you:
- Sealed bids — Your pricing stays private until settlement.
- No adverse selection — You see the intent, not a limit order that's already been front-run.
- Programmable responses — Use the MCP server to build automated RFQ response bots.
- Multi-chain settlement — Settle on whatever chain has the best liquidity for you.
Getting Started
As a Trader (via Claude or any MCP client)
Add this to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"hashlock": {
"command": "npx",
"args": ["-y", "@hashlock-tech/mcp"],
"env": {
"HASHLOCK_ACCESS_TOKEN": "your-siwe-token"
}
}
}
}
Then just ask Claude: "Create an intent to sell 5 ETH for USDC at minimum $3,200 per ETH."
As a Developer
npm install @hashlock-tech/mcp
The server is MIT-licensed. Fork it, extend it, build your own trading strategies on top.
- npm: @hashlock-tech/mcp
- GitHub: Hashlock-Tech/hashlock-mcp-server
- MCP Registry: io.github.Hashlock-Tech/hashlock
What's Next
We're working on:
- Multi-leg intents — Chain complex trades (e.g., sell BTC → buy ETH → stake on Lido) into a single atomic execution.
- Limit orders with expiry — Set a price and walk away. The MCP server watches and executes.
- Portfolio rebalancing — Tell your AI agent your target allocation, and it figures out the trades.
- More chains — Solana and Arbitrum are next.
The Bigger Picture
We believe the future of trading is declarative. You say what you want, not how to get it. AI agents handle execution. Protocols handle settlement. Humans handle strategy.
Hashlock Markets is the infrastructure layer for that future.
Hashlock Markets is built by Hashlock-Tech. Try it at hashlock.markets.
Questions? Reach out on GitHub or join the conversation.
Top comments (0)