Hashlock Markets
NPM · @HASHLOCK-TECH/MCP · 2 COMPONENTS
Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps.
Available components
Last scanned (41 minutes ago)
Scores higher than 23% of npm servers
Category Crypto and Web3
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 → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 209 of 215 dependencies we could resolve, 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 12 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: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox 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 →
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.
- 5 Nov 26 0
- Package version: 0.8.1 → 0.10.0 functional
- 4 Nov 26 0
- Package version: 0.8.1 → 0.10.0 functional
- 3 Nov 26 0
- Package version: 0.8.1 → 0.10.0 functional
- 2 Nov 26 0
- Package version: 0.8.1 → 0.10.0 functional
- 31 Oct 26 0
- Package version: 0.8.1 → 0.10.0 functional
- 29 Oct 26 0
- Package version: 0.8.1 → 0.10.0 functional
- 28 Oct 26 0
- Package version: 0.8.1 → 0.10.0 functional
- 26 Oct 26 0
- Package version: 0.8.1 → 0.10.0 functional
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 5 Nov 2026 · Analysed npm/@hashlock-tech/mcp@0.10.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| 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.10.0 |
| Rekor log index | 3420888279 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0d4af201e15e554e9c8e794e692801b740d4c63cc7d5fad4c88ce22d36ea98aafc767177999450e9a857adc3ea424a64c2bb8ca168a0753a9fafdc04d |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 14 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3pq3-5fj3-cg6v | CVE-2026-101898 | high | yes | |
| GHSA-44g4-m2mj-wpvx | CVE-2026-101899 | medium | yes | |
| GHSA-4hqw-qxg8-jxx2 | CVE-2026-101900 | medium | yes | |
| GHSA-542g-h47m-68v8 | CVE-2026-101901 | high | yes | |
| GHSA-9fr6-4gfg-395g | CVE-2026-101902 | medium | yes | |
| GHSA-c29m-xwm3-cm6r | CVE-2026-101903 | high | yes | |
| GHSA-j8rh-479h-cp32 | CVE-2026-101904 | medium | yes | |
| GHSA-m8m8-qj5v-23w3 | CVE-2026-101905 | high | yes | |
| GHSA-mghh-pgcx-3jjj | CVE-2026-101906 | high | yes | |
| GHSA-r4gj-5m52-g5wh | CVE-2026-101907 | high | yes | |
| GHSA-vh66-26gq-q6x8 | CVE-2026-101908 | medium | yes | |
| GHSA-x97p-jq2g-jp4f | CVE-2026-101909 | high | yes | |
| 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-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 209 packages
| Packages resolved | 209 |
|---|---|
| Stale | 72 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
How do I install the Hashlock Markets MCP server?
Hashlock Markets runs locally as an npm package, launched with npx -y @hashlock-tech/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @hashlock-tech/mcp
claude mcp add hashlock-tech-hashlock -- npx -y @hashlock-tech/mcp
What is the Hashlock Markets MCP server?
Hashlock Markets is an MCP server listed in the public MCP registry as io.github.Hashlock-Tech/hashlock. Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps. This page covers its npm package (@hashlock-tech/mcp).
Is the Hashlock Markets MCP server safe to use?
Hashlock Markets scores 44 out of 100 on VerifyMCP. We recorded 14 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the Hashlock Markets MCP server still maintained?
Hashlock Markets is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Hashlock Markets MCP server under?
Hashlock Markets declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.