hashlock-mcp
Hashlock Markets — sealed-bid intent-based crypto trading via MCP for AI agents. Atomic cross-chain settlement (Ethereum, Bitcoin, Sui) using HTLC. Six MCP tools for RFQ price discovery without information leakage and HTLC settlement without escrow or bridges. Canonical npm: @hashlock-tech/mcp.
README
@hashlock-tech/mcp
Hashlock Markets is an intent-based trading protocol for swapping any asset — crypto, RWAs, stablecoins — with private sealed bids and verified counterparties on Ethereum, Bitcoin, and SUI.
Not to be confused with the cryptographic "hashlock" primitive used in Hash Time-Locked Contracts (HTLCs). This package is the MCP server for the Hashlock Markets trading protocol and product at hashlock.markets.
Not affiliated with Hashlock Pty Ltd (hashlock.com), an independent Australian smart contract auditing firm. The two organizations share a similar name by coincidence only — distinct products, legal entities, jurisdictions, and founders.
What is this?
@hashlock-tech/mcp is the canonical Model Context Protocol server for Hashlock Markets. It lets AI agents (Claude, GPT, Cursor, Windsurf, any MCP-compatible client) create RFQs, respond as a market maker, fund HTLCs, and settle cross-chain atomic swaps across Ethereum, Bitcoin, and SUI.
Install
Option A (preferred) — Remote streamable-http
Connect Claude Desktop / Cursor / Windsurf directly to the Hashlock Markets MCP endpoint. No local install.
{
"mcpServers": {
"hashlock": {
"url": "https://hashlock.markets/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer <token from hashlock.markets/sign/login>"
}
}
}
}
Option B — Local stdio via npx
{
"mcpServers": {
"hashlock": {
"command": "npx",
"args": ["-y", "@hashlock-tech/mcp"],
"env": {
"HASHLOCK_ACCESS_TOKEN": "<token from hashlock.markets/sign/login>"
}
}
}
}
Config file location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Restart your client after editing.
Authentication
Hashlock Markets uses SIWE (Sign-In With Ethereum) bearer tokens.
- Visit hashlock.markets/sign/login
- Sign a message with your Ethereum wallet
- Receive a 7-day JWT
- Set it as
HASHLOCK_ACCESS_TOKEN(stdio) orAuthorization: Bearer <token>header (remote) - Re-sign after expiry
Available Tools
| Tool | Description |
|---|---|
create_rfq |
Create a Request for Quote (RFQ) to buy or sell crypto OTC. Broadcasts to market makers for sealed-bid responses. |
respond_rfq |
Market-maker side: submit a price quote in response to an open RFQ. |
create_htlc |
Fund a Hash Time-Locked Contract for atomic OTC settlement (records on-chain lock tx hash). |
withdraw_htlc |
Claim an HTLC by revealing the 32-byte preimage — settles the atomic swap. |
refund_htlc |
Refund an expired HTLC after timelock — only the original sender, only post-deadline. |
get_htlc |
Query current HTLC status for a trade (both sides, contract addresses, lock amounts, timelocks). |
All tools support three chains: Ethereum (EVM), Bitcoin (wrapped HTLC), and SUI (Move HTLC).
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
HASHLOCK_ACCESS_TOKEN |
Yes | — | 7-day SIWE JWT from hashlock.markets/sign/login |
HASHLOCK_ENDPOINT |
No | https://hashlock.markets/api/graphql |
GraphQL endpoint override (rarely needed) |
Tool Examples
Create an RFQ
"Create an RFQ to sell 2 ETH for USDT"
Tool: create_rfq
Input: { baseToken: "ETH", quoteToken: "USDT", side: "SELL", amount: "2.0" }
Output: { rfqId, broadcast status }
Respond to an RFQ
"Quote 3400 USDT per ETH on RFQ abc-123"
Tool: respond_rfq
Input: { rfqId: "abc-123", price: "3400.00", amount: "2.0" }
Check HTLC Status
"What's the HTLC status for trade xyz-789?"
Tool: get_htlc
Input: { tradeId: "xyz-789" }
Fund an HTLC
"Record my ETH lock transaction for trade xyz-789"
Tool: create_htlc
Input: { tradeId: "xyz-789", txHash: "0xabc...", role: "INITIATOR", chainType: "evm" }
Claim with Preimage
"Claim the HTLC using the preimage"
Tool: withdraw_htlc
Input: { tradeId: "xyz-789", txHash: "0xdef...", preimage: "0x1234..." }
Deprecated legacy packages
Do not use these — they depended on an intent REST API that was never shipped, and are superseded by @hashlock-tech/mcp:
hashlock-mcp-server(unscoped, npm) — deprecated 2026-04-19langchain-hashlock(PyPI) — superseded for MCP-based integrations
Links
- Website: hashlock.markets
- MCP Endpoint (remote): hashlock.markets/mcp
- SIWE Login: hashlock.markets/sign/login
- GitHub: Hashlock-Tech/hashlock-mcp
- MCP Registry: io.github.Hashlock-Tech/hashlock
- npm: @hashlock-tech/mcp
- llms.txt: hashlock.markets/llms.txt
License
MIT © Hashlock Corp.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。