Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/hashlock-tech/hashlock-mcp/hashlockgit clone --depth 1 https://github.com/Hashlock-Tech/hashlock-mcpGrade A, and why
hashlock scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"hashlock": {
"command": "npx",
"args": [
"-y",
"@hashlock-tech/mcp",
"-y"
],
"env": {
"HASHLOCK_EVM_KEY": "",
"HASHLOCK_TRON_KEY": "",
"HASHLOCK_BTC_KEY": "",
"HASHLOCK_TOKEN": "",
"HASHLOCK_API_URL": "https://dev.hashlock.markets/api",
"HASHLOCK_EVM_RPC": "https://ethereum-sepolia-rpc.publicnode.com",
"HASHLOCK_TRON_HOST": "https://nile.trongrid.io"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 19 lines scan A aa230c0f1e6c
hashlock is an MCP server published in the GitHub repository Hashlock-Tech/hashlock-mcp (0 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
alloc-context
Portfolio-aware crypto context — CEX or wallet holdings, holdings-scoped market, optional allocation analysis. Runs locally from the alloc-context Python package.
bitcoin-mcp
MCP server for Bitcoin — 49 tools for AI agents to save money on fees. Zero config, works out of the box. Runs locally from the bitcoin-mcp Python package. Needs 5 environment variables to run.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.
verdictswarm
Every tool has an answer — your agent needs a decision. MCP server for the VerdictSwarm pre-trade check: a machine-readable avoid/caution/clear before your agent trades, plus intended-size exit feasibility and holder-cluster attribution on Solana. Runs locally from the verdictswarm-mcp Python package. Needs 3…
verdictswarm-mcp
Every tool has an answer — your agent needs a decision. MCP server for the VerdictSwarm pre-trade check: a machine-readable avoid/caution/clear before your agent trades, plus intended-size exit feasibility and holder-cluster attribution on Solana. Runs locally from the verdictswarm-mcp Python package. Needs 1…
bsv-wallet
MCP server "bsv-wallet" as configured in Calhooon/bsv-wallet-cli. Launched with cargo run --release --manifest-path mcp/Cargo.toml. Needs 1 environment variable to run.