# Hashlock Markets (io.github.Hashlock-Tech/hashlock@1.8.1) > Source: > Published: 2026-09-15 14:53:03+00:00 [← Index](https://mcpindex.ai/leaderboard) # Hashlock Markets Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps. Testnet. The current version, v1.8.1, was published to the official MCP registry on 2026-09-15. It is distributed as @hashlock-tech/mcp on npm, filed under Other by this index, and declares 8 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](https://mcpindex.ai/stats) put this record in context. ## Using Hashlock Markets in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that). Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less ``` uv tool install mcpindex-gate && mcpindex-config-wire ``` [method](https://mcpindex.ai/methodology) Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. `mcpindex.integrity.description` passINFO evidence“No malicious instructions found”via static_description - - Semantic screen only - the deterministic conformance probe has not run on this server - - Confidence is reported but not yet calibrated (v1) - - Screen reads the tool description, not the live behavior - - advisory - - registry description only no input schema - - screen model 8b - - Still current: the description we screened is unchanged, re-checked against the registry - - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page. Own this server? [Screen its description →](https://mcpindex.ai/screen) ## That verdict was true at screening time (snapshot 2026-09-15). Contracts can change after screening, with no version bump. The gate pins Hashlock Markets’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. [See your first HOLD in 2 minutes →](https://mcpindex.ai/guides/install-the-gate-first-hold) Related: [how to trust an MCP server](https://mcpindex.ai/guides/how-to-trust-an-mcp-server) · [screen before install](https://mcpindex.ai/guides/screen-mcp-server-before-install) · [silent contract drift](https://mcpindex.ai/guides/mcp-silent-contract-drift) People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land. ``` [Independent trust record for Hashlock Markets](https://mcpindex.ai/server/io-github-hashlock-tech-hashlock) - screening verdict, registry provenance, and contract drift monitoring. Independent trust record for Hashlock Markets - screening verdict, registry provenance, and contract drift monitoring. ``` A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does. ``` [![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-hashlock-tech-hashlock)](https://mcpindex.ai/server/io-github-hashlock-tech-hashlock) mcpindex verdict ``` `HASHLOCK_EVM_KEY` EVM private key (0x, 32-byte) for autonomous SIWE login + EVM settlement — dedicated TESTNET key `HASHLOCK_TRON_KEY` TRON private key (64-hex) for autonomous login + TRON settlement `HASHLOCK_BTC_KEY` Bitcoin WIF (signet) for autonomous BIP-322 login + BTC HTLC claims `HASHLOCK_SOLANA_KEY` Solana secret key (base58, 32- or 64-byte) for autonomous login + Solana HTLC settlement `HASHLOCK_TOKEN` A ready JWT (alternative to a key) `HASHLOCK_API_URL` REST API endpoint override `HASHLOCK_EVM_RPC` EVM RPC the agent submits fund/claim through `HASHLOCK_TRON_HOST` TRON full host [methodology](https://mcpindex.ai/methodology) [AgentRoamai.agentroam/agentroam](https://mcpindex.ai/server/ai-agentroam-agentroam) Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order. [Authoryzeai.authoryze/authoryze](https://mcpindex.ai/server/ai-authoryze-authoryze) Give your AI agent a spending limit: approval controls and single-use virtual cards. [Crystallize MCPio.github.HayoDev/crystallize-mcp](https://mcpindex.ai/server/io-github-hayodev-crystallize-mcp) Crystallize headless commerce tools for AI agents via Model Context Protocol