Loading the registry…
Hashlock Markets — the settlement layer for the agent economy, as MCP tools. Non-custodial cross-chain OTC: sealed RFQ + price negotiation + HTLC atomic settlement (both legs settle or both refund; no custodian). BTC ↔ EVM / TRON. TESTNETS ONLY for now (Ethereum Sepolia, TRON Nile, Bitcoin signet) — mainnet after the security-hardening gate. Autonomous-agent ready: SIWE login with the agent's own key, swap secrets generated locally. NOT affiliated with Hashlock Pty Ltd (hashlock.com).
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
3 critical findings reported by agent-audit-kit, 1 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/Hashlock-Tech/hashlock-mcp, 32 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @hashlock-tech/mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.5s
v2.0.11
9 findings · 6.6s
v0.3.26
17 findings · 0.9s
v0.1.0
4 findings · 27.1s
v0.1.0
0 findings · 27.1s
v0.1.0
0 findings · 18.0s
No report in this scan: capslock, govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 4, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 30 findings across every scanner that examined this package. 2 of 3 findings rated critical by their scanner were among the dismissals.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/architecture/SKILL.md · reported by cisco-skill-scanner
2 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-INDIA-PII-001 · Files: src/__tests__/client.test.ts · reported by agent-audit-kit
1 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/ci.yml · reported by agent-audit-kit
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
4 AAK-MCP-018
Files: src/tools.ts, src/index.ts, src/http/tools.ts and 1 more · reported by agent-audit-kit
4 AAK-SECRET-004
Files: src/config.ts, src/chains/btc.ts · reported by agent-audit-kit
4 DATA_EXFIL_JS_NETWORK
Files: /repo/src/chains/btc.ts, /repo/src/client.ts, /repo/src/http/v1-client.ts · reported by cisco-skill-scanner
4 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/chains/tron.ts, /repo/src/client.ts, /repo/src/http/v1-client.ts · reported by nerlo-behavioral
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-001
Files:
Critical DNS rebind vulnerability and secrets exposed to network egress
The artifact contains a critical DNS rebind vulnerability in `src/http/server.ts`, which could allow bypassing security controls. Multiple secrets are present in the installed code, specifically in `src/chains/btc.ts` and `src/config.ts`. These secrets are also observed being sent over the network from `src/chains/tron.ts`, `src/client.ts`, and `src/http/v1-client.ts`. Additionally, the artifact uses an Anthropic SDK in `src/index.ts` and has stateless session management in `src/http/server.ts`.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
1 AAK-MCP-STATELESS-001
Files: src/http/server.ts · reported by agent-audit-kit
1 AAK-OAUTH-005
Files: src/http/server.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner