Server data from the Official MCP Registry
OTC crypto trading with HTLC atomic settlement on Ethereum and Bitcoin
OTC crypto trading with HTLC atomic settlement on Ethereum and Bitcoin
Valid MCP server (2 strong, 4 medium validity signals). 4 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (5/5 approved).
6 files analyzed · 5 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: HASHLOCK_ACCESS_TOKEN
Environment variable: HASHLOCK_ENDPOINT
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-barissozen-hashlock-mcp": {
"env": {
"HASHLOCK_ENDPOINT": "your-hashlock-endpoint-here",
"HASHLOCK_ACCESS_TOKEN": "your-hashlock-access-token-here"
},
"args": [
"-y",
"@hashlock-tech/mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Hashlock Markets — the atomic settlement layer for the agent economy. HTLC-based atomic settlement: live on Ethereum and Sui mainnets, with Bitcoin mainnet-ready via P2WSH HTLC scripts (no contract to deploy; signet-validated). No bridges, no custodians, no trust assumptions. Sealed-bid RFQ + HTLC fused into one atomic operation. The settlement primitive AI agents use to trade across chains. MCP-native (6 tools).
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.
@hashlock-tech/mcp is the canonical Model Context Protocol server for Hashlock Markets — the atomic settlement layer for the agent economy. 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 on Ethereum and Sui mainnets, with Bitcoin mainnet-ready via P2WSH HTLC scripts (no contract to deploy; signet-validated). Expanding to Base, Arbitrum, Solana, TON. No bridges, no custodians, no trust assumptions.
Hashlock Markets features 5 industry-first primitives: BTC Collateral Vaults (Sui-native via Hashi), Forward OTC Settlement (T+24h/T+48h), Verified Counterparty Directory, Multi-leg Trade Atomicity, and Execution Rewards with Tiered KYC. Three interaction modes: AI ↔ AI, AI ↔ Human, Human ↔ Human.
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>"
}
}
}
}
{
"mcpServers": {
"hashlock": {
"command": "npx",
"args": ["-y", "@hashlock-tech/mcp"],
"env": {
"HASHLOCK_ACCESS_TOKEN": "<token from hashlock.markets/sign/login>"
}
}
}
}
Config file location:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonRestart your client after editing.
Hashlock Markets uses SIWE (Sign-In With Ethereum) bearer tokens.
HASHLOCK_ACCESS_TOKEN (stdio) or Authorization: Bearer <token> header (remote)| 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).
| 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) |
"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 }
"Quote 3400 USDT per ETH on RFQ abc-123"
Tool: respond_rfq
Input: { rfqId: "abc-123", price: "3400.00", amount: "2.0" }
"What's the HTLC status for trade xyz-789?"
Tool: get_htlc
Input: { tradeId: "xyz-789" }
"Record my ETH lock transaction for trade xyz-789"
Tool: create_htlc
Input: { tradeId: "xyz-789", txHash: "0xabc...", role: "INITIATOR", chainType: "evm" }
"Claim the HTLC using the preimage"
Tool: withdraw_htlc
Input: { tradeId: "xyz-789", txHash: "0xdef...", preimage: "0x1234..." }
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 integrationsBe the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.