Log inSubmit server
Hashlock MCP logo

Hashlock MCP

by Hashlock-Tech

Cross-chain OTC trading with sealed RFQs, negotiation, and non-custodial HTLC settlement for BTC, EVM, TRON, and Solana.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Hashlock MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "hashlock-tech-hashlock-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hashlock-tech/mcp"
      ],
      "env": {
        "HASHLOCK_API_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 17 tools correctly (3d ago).

Overview

Hashlock-Tech/hashlock-mcp exposes Hashlock Markets as MCP tools for cross-chain over-the-counter trading. Agents can browse assets and RFQs, create or negotiate orders, and track deals settled through hash time-locked contracts. Local stdio mode can sign funding, claims, and refunds with configured wallet keys, while the hosted Streamable HTTP endpoint returns unsigned transactions for users to sign. Use it when an agent needs BTC, EVM, TRON, or Solana swaps without bridges or custodial key storage.

Use cases

  • Browse cross-chain assets and public RFQs
  • Create private fixed-price OTC orders
  • Negotiate prices between trading agents
  • Monitor HTLC funding and timelocks
  • Fund, claim, or refund swaps with agent-owned keys

Key features

  • Sealed RFQ and private-order workflows
  • Cross-chain HTLC atomic settlement
  • Negotiation threads with price validation
  • Local autonomous wallet signing
  • Hosted unsigned transaction mode
  • BTC, EVM, TRON, and Solana support

Tools17

What Hashlock MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

19/19 checks healthy over the last 79d

What it can do

From the 17 tools this server returned when we ran it.

Handles credentials · 5Makes network requests · 2Read-only tools · 17
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age199 days
Maintainers2

Observed 2026-10-26 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @hashlock-tech/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.3kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed17Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Hashlock MCP works

What Hashlock-Tech/hashlock-mcp does

Hashlock-Tech/hashlock-mcp connects MCP clients to Hashlock Markets, a platform for cross-chain OTC orders. It supports sealed request-for-quote workflows: an agent can inspect supported assets, view public requests, publish a public RFQ or private fixed-price order, receive quotes, and negotiate within a deal thread.

Once both parties agree on the other side’s price, the platform creates an HTLC swap. The settlement model is designed so each leg is either claimed or refunded after its timelock. The service does not hold trading funds or wallet keys. Swap preimages are generated locally in the stdio package, and only their SHA-256 hashlocks are sent to the service.

How it works

The package can run locally over stdio or remotely at https://hashlock.markets/mcp using Streamable HTTP. Local mode uses the agent’s configured wallet keys for authentication and, when enabled, for on-chain settlement. Remote mode uses wallet authorization and supplies unsigned funding, claim, or refund transactions for signing outside the service.

A typical workflow is:

  1. Inspect the asset registry and open RFQs.
  2. Create an order or respond to an existing request with a price.
  3. Negotiate, accept the other party’s price, and create the deal.
  4. Set receive and refund addresses for the relevant chains.
  5. Monitor funding, timelocks, and transaction hashes.
  6. Retrieve the local deal secret when both legs are funded, then claim or report an out-of-band claim.

Supported mainnet networks include Bitcoin, Ethereum, Base, Robinhood Chain, TRON, and Solana.

Setup and configuration

Install and launch the npm package with an API base URL:

bash
HASHLOCK_API_URL=https://hashlock.markets/api npx -y @hashlock-tech/mcp

HASHLOCK_API_URL is required. With no wallet key or token, the server still supports read-only asset and RFQ browsing. Autonomous local settlement can use HASHLOCK_EVM_KEY, HASHLOCK_TRON_KEY, HASHLOCK_BTC_KEY, or HASHLOCK_SOLANA_KEY; HASHLOCK_TOKEN provides a ready JWT instead of signing in with a key.

Optional settings cover application share links, EVM and TRON RPC access, and the local secrets file. Use a dedicated wallet containing only the funds intended for trading.

Tools and capabilities

The MCP interface includes tools for:

  • Listing assets and open RFQs, retrieving individual RFQs, and identifying the authenticated account.
  • Creating, cancelling, responding to, and negotiating RFQs and private orders.
  • Reading deal threads, negotiation history, HTLC state, funding progress, timelocks, and transaction hashes.
  • Setting settlement addresses and retrieving the locally stored deal preimage after both swap legs are funded.
  • Reporting claims made outside the server.
  • Funding, claiming, or refunding a swap leg autonomously in local mode for EVM, TRON, Bitcoin, and Solana.

Limitations and notes

Remote mode does not sign transactions, store wallet keys, or store the swap preimage. Solana transactions are composed by the service and signed by the agent using the bytes returned to it. Solana wallet ownership may need to be proven before posting, quoting, accepting, or using whoami for an order involving Solana.

Accepting a negotiation must name the price being accepted, and an outdated price is refused. A counteroffer or the caller’s own quote counts as that party’s acceptance, so agents should accept the other side’s quoted price. Local signing depends on correctly configured chain keys, settlement addresses, and RPC settings.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Hashlock MCP

Hashlock-Tech/hashlock-mcp is an MCP server that connects AI agents to Hashlock Markets for cross-chain OTC trading. Its main tools browse assets and RFQs, create and negotiate orders, track HTLC deals, manage settlement addresses, and fund, claim, or refund swap legs with agent-owned wallet keys.

Install it by launching the npm package with `HASHLOCK_API_URL=https://hashlock.markets/api npx -y @hashlock-tech/mcp`. Add the command and API URL to an MCP client’s server configuration. Wallet keys are optional for read-only browsing and required for autonomous local settlement.

Yes, Hashlock-Tech/hashlock-mcp works with Cursor through its local stdio configuration. Add `npx -y @hashlock-tech/mcp` as the command and set `HASHLOCK_API_URL`; add the relevant chain key environment variables if the agent must sign settlements.

Yes, use the hosted Streamable HTTP endpoint for a non-custodial flow that returns unsigned funding, claim, and refund transactions. Local stdio mode can sign with keys supplied to the process, but the service itself does not hold those keys or the swap preimage.

Hashlock-Tech/hashlock-mcp supports Bitcoin, Ethereum, Base, Robinhood Chain, TRON, and Solana on mainnet. Local autonomous funding, claiming, and refunding use configured keys for EVM, TRON, Bitcoin, and Solana, while Solana transactions are signed from bytes composed by the service.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHashlock MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hashlock-tech-hashlock-mcp?style=directory)](https://allmcps.com/mcp/hashlock-tech-hashlock-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/hashlock-tech-hashlock-mcp"><img src="https://allmcps.com/api/badge/hashlock-tech-hashlock-mcp?style=directory" alt="Hashlock MCP on AllMCPs" /></a>