Skip to content

Hashlock-Tech/hashlock-mcp

Repository files navigation

@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.

npm License: MIT MCP Registry

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.

  1. Visit hashlock.markets/sign/login
  2. Sign a message with your Ethereum wallet
  3. Receive a 7-day JWT
  4. Set it as HASHLOCK_ACCESS_TOKEN (stdio) or Authorization: Bearer <token> header (remote)
  5. 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-19
  • langchain-hashlock (PyPI) — superseded for MCP-based integrations

Links

License

MIT © Hashlock Corp.

About

Canonical MCP server for Hashlock Markets — sealed-bid intent trading + HTLC atomic settlement for AI agents. Published as @hashlock-tech/mcp on npm.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors