convez.ai
MCP ServerFinanceiroAvançado
Hashlock-Tech

Hashlock Markets — Camada Atômica de Liquidação

Hashlock-Tech/hashlock-mcp

Liquidação atômica cross-chain para agentes IA — sem bridges, sem custódia

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP para liquidação atômica cross-chain sem custódia, combinando RFQs selados com HTLCs numa única operação. Ativo em Ethereum e Sui, pronto para Bitcoin mainnet. Permite que agentes IA negociem assets entre blockchains com garantia criptográfica de atomicidade.

Instalação

$npx convez-ai Hashlock-Tech/hashlock-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
50%
Último commit
há 1 dia
Versão
v1.14.0
Issues abertas
0
Contribuidores
3

Casos de uso

  • Agentes IA executando swaps atômicos entre Ethereum, Sui e Bitcoin
  • Desks OTC institucional automatizando RFQs e settlement
  • Trading contra-party com verificação de identidade em cadeia

Veredito

Produto sofisticado de liquidação descentralizada com integração MCP madura. Recomendado para quem precisa de settlement atômico cross-chain sem custódia — exige domínio de cripto e HTLC para explorar todo potencial.

README

A tradução para o português deste README ainda está na fila.

@hashlock-tech/mcp

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.

npm License: MIT MCP Registry smithery badge

What is this?

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

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

ToolDescription
create_rfqCreate a Request for Quote (RFQ) to buy or sell crypto OTC. Broadcasts to market makers for sealed-bid responses.
respond_rfqMarket-maker side: submit a price quote in response to an open RFQ.
create_htlcFund a Hash Time-Locked Contract for atomic OTC settlement (records on-chain lock tx hash).
withdraw_htlcClaim an HTLC by revealing the 32-byte preimage — settles the atomic swap.
refund_htlcRefund an expired HTLC after timelock — only the original sender, only post-deadline.
get_htlcQuery 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

VariableRequiredDefaultDescription
HASHLOCK_ACCESS_TOKENYes—7-day SIWE JWT from hashlock.markets/sign/login
HASHLOCK_ENDPOINTNohttps://hashlock.markets/api/graphqlGraphQL 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

Architecture

How this server is structured, the six tools, the create_rfq intent compiler, and how it connects to the Hashlock Markets backend (and the @hashlock-tech/sdk it wraps): docs/architecture/ARCHITECTURE.md · Русский.

Ver o original no GitHub

Bom para

Relacionados