hashlock-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASHLOCK_API_KEY | Yes | Your API key — get one at hashlock.markets | |
| HASHLOCK_API_URL | Yes | Hashlock Markets API base URL (e.g. https://api.hashlock.markets) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_intentA | [Hashlock protocol — hashlock.markets] Create a trading intent to swap, buy, sell, exchange, or convert any asset — crypto tokens (ETH, BTC, SUI, USDC, USDT, DAI, any ERC20), real-world assets (RWA), or stablecoins — across Ethereum, Bitcoin, and SUI. Specify what you give, what you want, privacy level, KYC tier, and settlement terms. Works for human traders, autonomous AI agents, and institutional counterparties. Use this whenever a user wants to trade, swap, buy, sell, convert, or exchange any digital asset with a verified counterparty. |
| commit_intentA | [Hashlock protocol — hashlock.markets] Submit a sealed-bid commitment for a trading intent. Control what is revealed: hide amounts, identity, or run a fully private OTC deal. Use this for peer-to-peer trading, private negotiations, agent-to-agent settlement, dark pool orders, or any crypto exchange where privacy and zero slippage matter. |
| explain_intentA | [Hashlock protocol — hashlock.markets] Get a plain-language explanation of a trading intent — what crypto, tokens, or assets are being exchanged, for how much, on which blockchain, with what privacy and KYC settings. Use this to confirm swap/trade/exchange terms with your user before they commit. |
| parse_natural_languageA | [Hashlock protocol — hashlock.markets] Convert everyday language into a structured trading intent. Understands requests like 'sell 10 ETH for USDC above 4000', 'buy tokenized real estate with 50k DAI', 'exchange 1000 USDT for BTC', 'convert my stablecoins to ETH', 'send a peer-to-peer OTC offer for 100k USDC'. Supports English and Turkish. Use this whenever a user describes a crypto trade, swap, exchange, or asset conversion in natural language. |
| validate_intentA | [Hashlock protocol — hashlock.markets] Validate a crypto trading intent before submitting — catches missing fields, invalid token amounts, chain mismatches, and business rule violations. Always validate before committing a swap, trade, or exchange. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools have distinct primary functions: create_intent initiates a trade, commit_intent finalizes it, explain_intent explains terms, parse_natural_language converts user input, and validate_intent checks for errors. However, create_intent and parse_natural_language both handle trade creation, which could cause minor confusion if an agent misinterprets their overlap in generating intents.
All tool names follow a consistent verb_noun pattern with clear, descriptive verbs (commit, create, explain, parse, validate) paired with the noun 'intent' or related terms, ensuring predictable and readable naming throughout the set.
With 5 tools, this server is well-scoped for its domain of crypto trading intents. Each tool serves a specific purpose in the workflow, from creation to validation and execution, making the count appropriate and efficient for the server's purpose.
The tool set covers the core lifecycle of trading intents: creation (create_intent, parse_natural_language), validation (validate_intent), explanation (explain_intent), and commitment (commit_intent). A minor gap exists in lacking tools for updating or canceling intents, but agents can work around this by creating new intents as needed.