Other · Local MCP server
Hashlock Markets
Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps. Testnet.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Hashlock-Tech/hashlock- Version
- 1.8.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-15
- Updated
- 2026-09-15
- Publisher
- Hashlock-Tech (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Hashlock-Tech) · how
- Website
- hashlock.markets
- Repository
- github.com/Hashlock-Tech/hashlock-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @hashlock-tech/mcp | 0.8.1 | stdio |
How to connect Hashlock Markets
Hashlock Markets runs locally from a Node.js package published to the npm registry: @hashlock-tech/mcp version 0.8.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @hashlock-tech/mcp@0.8.1. It reads these environment variables: HASHLOCK_EVM_KEY (secret), HASHLOCK_TRON_KEY (secret), HASHLOCK_BTC_KEY (secret), HASHLOCK_SOLANA_KEY (secret), HASHLOCK_TOKEN (secret), HASHLOCK_API_URL, HASHLOCK_EVM_RPC and HASHLOCK_TRON_HOST; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"hashlock": {
"command": "npx",
"args": [
"-y",
"@hashlock-tech/mcp@0.8.1"
],
"env": {
"HASHLOCK_EVM_KEY": "<secret>",
"HASHLOCK_TRON_KEY": "<secret>",
"HASHLOCK_BTC_KEY": "<secret>",
"HASHLOCK_SOLANA_KEY": "<secret>",
"HASHLOCK_TOKEN": "<secret>",
"HASHLOCK_API_URL": "<value>",
"HASHLOCK_EVM_RPC": "<value>",
"HASHLOCK_TRON_HOST": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| HashMCP server for cryptographic hashing - MD5, SHA-1, SHA-256, SHA-384, SHA-512. | Local · stdio |
| Hash Digest ToolComputes MD5, SHA1, SHA256, SHA512, and CRC32 digests from text, base64, or hex input. | Remote · HTTPLive check: ✓ handshake |
| Hash Generator APICryptographic hashing - MD5, SHA1, SHA256, SHA512, bcrypt. x402 micropayment. | Remote · SSELive check: ✗ no handshake |
| Hashfile MCPHash-anchored file editing with surgical precision over file editing and ironclad control of access. | Local · stdio |
| HashnPrivate shared file system for agents: workspaces, invites, shared files. | Remote · HTTPLive check: ✓ handshake |
| HatchHosting for AI agents: publish a live website in one tool call, ephemeral or forever. | Remote · HTTPLive check: ✓ handshake |
| Haulage Uk Compliance MCPUK Operator Licence, tachograph, drivers' hours, DVSA roadside checks for UK haulage operators a... | Local · stdio |
| Hci Quality MCPInterface observations and explicit GOMS/KLM, Fitts, Hick-Hyman and cognitive walkthrough models. | Local · stdio |