Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Hashlock Markets

NPM · @HASHLOCK-TECH/MCP · SCANNED AUG 3

Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps. Testnet.

Available components

npm · @hashlock-tech/mcp 44
+26 this week 44 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects ws 8.17.1, reached via tronweb > ethers > ws. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (206 of 214), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Hashlock-Tech/hashlock-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @hashlock-tech/mcp

# add to Claude Code
claude mcp add hashlock-tech-hashlock -- npx -y @hashlock-tech/mcp
# add to Codex CLI
codex mcp add hashlock-tech-hashlock -- npx -y @hashlock-tech/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hashlock-tech-hashlock": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@hashlock-tech/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hashlock-tech-hashlock --command npx --arg -y --arg @hashlock-tech/mcp
# ~/.hermes/config.yaml
mcp_servers:
  hashlock-tech-hashlock:
    command: "npx"
    args: ["-y", "@hashlock-tech/mcp"]
// mcp.json
{
  "mcpServers": {
    "hashlock-tech-hashlock": {
      "command": "npx",
      "args": [
        "-y",
        "@hashlock-tech/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 −20
    • CVE-2026-48779 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • Stability: 0.23 → unverified ▼ security
    • Known CVEs: partial → fail ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: Hashlock-Tech/hashlock-mcp security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.4.1 → 0.5.1 functional
  • 2 Aug 26 +47
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Malware scan: unverified → pass ▲ security
    • Maintenance: unverified → pass ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → good ▲ functional
    • License: unverified → pass ▲ functional
    • Licence: MIT functional
  • 31 Jul 26 −24
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +6
    • Source repository: fail → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
  • 28 Jul 26 +17
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: unverified functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 18

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@hashlock-tech/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
Hashlock-Tech/hashlock-mcp
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/Hashlock-Tech/hashlock-mcp/.github/workflows/release.yml@refs/tags/v0.5.1
Rekor log index:
2275168538
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:28af183912ed98bbab64a2a09d8b4706b38e8b56956487981137fd0dfd1d5bb1368cfbb4c6c7b0ecffbd62bccdd6205c46a5b4f81a49c897df2574eba
Discovery method:
attestation_endpoint
Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-848j-6mx2-7j84 CVE-2025-14505 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L no
GHSA-58qx-3vcg-4xpx CVE-2026-45736 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N yes
GHSA-96hv-2xvq-fx4p CVE-2026-48779 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
Dependencies 206 packages

206 packages in the resolved dependency tree · 162 deprecated · 69 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.