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

Locker Protocol Agentic

NPM · @LOCKER-PROTOCOL/AGENT-WALLET-HYPERLIQUID-TRADER-MCP

Hyperliquid perps for AI agents. The agent trades; the keys stay offline in Locker Vault.

+31 this week 65 Trust /100

Last scanned (13 hours ago)

Scores higher than 37% of npm servers

Category Finance and Payments

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @locker-protocol/agent-wallet-hyperliquid-trader > @locker-protocol/agent-wallet-vault > @keystonehq/bc-ur-registry-eth > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 69 of 184 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4516 tokens (~107/item across 42 items; 42 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +15
    • Tool safety: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
    • Package version: 2.4.1 → 2.4.3 functional
    • Package version: 2.3.0 → 2.4.2 functional
  • 15 Oct 26 +15
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 100 functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
    • Package version: 2.3.0 → 2.4.1 functional
    • Package version: 2.3.0 → 2.4.0 functional
  • 14 Oct 26 0
    • Package version: 2.2.0 → 2.3.0 functional
  • 12 Oct 26 0
    • Package version: 2.0.2 → 2.2.0 functional
  • 9 Oct 26 34

    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 18 Oct 2026 · Analysed npm/@locker-protocol/agent-wallet-hyperliquid-trader-mcp@2.4.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 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-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 184 packages
Packages resolved 184
Deprecated 1
Stale 67
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 42 exposed · ~4,238 tokens

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 →

Tool Tokens
copy_resume ~26

Start a background process again for each copy left paused (after a restart of the computer).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

copy_start ~391

Start a background process that copies a trader for some days: every order of theirs is mirrored, sized as asked, with the real fees; what the leader reduces is reduced by the same share. In simulation by default, on a simulation account of its own, and nothing is signed. With live, the orders go to the real account through the guardian, each checked against the policy and the mandate the user signed on their phone. The process outlives this call and keeps running after the terminal closes, until copy_stop or the days run out.

NameTypeReqDescription
at_endstring–What becomes of its positions when the days run out: keep (the default, left as they are) or close (closed at market, reduce-only); copy_stop keeps them either way
budgetnumber–Simulated USD for this copy (default 1000)
daysnumber–How long it copies (default 7, at most 30)
fixed_marginnumber–With fixed: the USD of margin for each opening, at most the budget
leaderstringyesThe trader to copy (0x...)
liveboolean–On the real account instead of simulation: needs the guardian unlocked by the user and a mandate they signed naming this trader, with room in its copy budget
max_scalenumber–With proportional: at most this many times the leader's size (default 1)
percentnumber–With percent: the share of the copy's equity used as the margin of each opening
sizingstring–How each opening is sized: proportional (the default: the leader's size times the copy's equity over the leader's, at most max_scale times the leader's size), mirror (the leader's size), percent (tha…

No output schema declared.

No examples provided.

copy_status ~38

The copies in simulation: each one's equity and gain, running or (with all) ended.

NameTypeReqDescription
allboolean–The ended copies too

No output schema declared.

No examples provided.

copy_stop ~57

Stop the background process copying a trader, or every one; the result stays in copy_status with all: true.

NameTypeReqDescription
allboolean–Every copy (instead of leader)
leaderstring–The trader copied (0x...)

No output schema declared.

No examples provided.

doctor ~21

Check the setup, sign nothing: each check with what to do.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hyperkeel_alerts ~70

The alerts on the moves of the traders followed (notifications, email): on from 250k, 1m or 5m dollars, or off.

NameTypeReqDescription
offboolean–Turn the alerts off
thresholdstring–Alert on moves of at least this many dollars

No output schema declared.

No examples provided.

hyperkeel_brief ~40

The state of the market in one answer, from hyperkeel: the movers, funding, liquidations and large trades. No account needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hyperkeel_follow ~45

Follow a trader on hyperkeel: its moves reach the user with their alerts. Moves no funds.

NameTypeReqDescription
addressstringyesThe trader's account (0x...)

No output schema declared.

No examples provided.

hyperkeel_follows ~32

The traders the user follows on hyperkeel, where their moves are sent, and the latest ones.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hyperkeel_leaders ~55

The first accounts of a Hyperliquid leaderboard, from hyperkeel: their PnL, volume and ROI over the period. No account needed.

NameTypeReqDescription
windowstring–The period ranked (default day)

No output schema declared.

No examples provided.

hyperkeel_status ~46

Whether this computer is connected to hyperkeel.com (market data, alerts), with which account, until when. Connecting is the user's: `lpa hyperkeel login`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hyperkeel_unfollow ~34

Stop following a trader on hyperkeel.

NameTypeReqDescription
addressstringyesThe trader's account (0x...)

No output schema declared.

No examples provided.

journal ~65

What was done, refused, and paid: orders, refusals, deposits, and the fees total.

NameTypeReqDescription
limitinteger–How many lines (default 50)
sincestring–A duration back from now (24h, 7d) or a date

No output schema declared.

No examples provided.

mandate_revoke ~37

Drop the mandate: the guardian opens nothing under it until the user signs a new one. Closing positions stays allowed. It only restricts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mandate_show ~63

The mandate the user signed, when there is one: the limits the guardian applies before every opening on top of the policy (size, leverage, markets, orders and notional per day, the fee recipient, live copies), its end, and whether it is in force.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mandate_sign ~263

Sign the limits of the agent with the user's own wallet (Locker Vault, their extension or their mobile wallet): the policy's bounds, a notional ceiling per day, the uses it allows (orders, live copies, the pilot) and the traders live copies may follow, for the agent's life at most (180 days). This tool signs nothing and returns the command the user types in their own terminal.

NameTypeReqDescription
actionsstring–The uses it allows, comma separated: trade (orders from the agent), copy (live copies, with copy_leaders), pilot (orders the pilot decides itself). Default: trade, and copy with copy_leaders
copy_budgetnumber–With copy_leaders: the USD the live copies may use
copy_leadersstring–Traders live copies may follow, comma separated (0x...,0x...)
copy_onlyboolean–Live copies only, no orders from the agent
daysnumber–How long it lasts (default and at most 180, the agent's life, never past the agent)
max_notional_per_daynumber–The most notional opened per UTC day, in USD (default: the policy's largest order times its orders per day)

No output schema declared.

No examples provided.

paper_init ~66

Open a simulation account: fills on the real order book with the real fees, no key and no vault needed.

NameTypeReqDescription
budgetnumber–The simulation budget in USD (default 1000)
resetboolean–Start an existing simulation account over (its history is lost)

No output schema declared.

No examples provided.

paper_off ~14

Back to the real account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

paper_on ~32

Every perps tool uses the simulation account until paper_off; modify, cancel and the movements of funds are refused meanwhile.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

paper_record ~161

Record the market into a local tape for paper_replay: the 1 m, 5 m, 1 h and 4 h candles of each market and its funding history, appended to what is already recorded. One call reaches about a day back on the 1 m band, so the tape grows by running this again over days. Nothing is signed and no key is read.

NameTypeReqDescription
coinsstring–The markets to record, comma separated (BTC,ETH); omit for the busiest ones
min_vlmnumber–Only the markets with at least this much 24 h volume in USD (default 5000000)
topinteger–How many markets to record, by 24 h volume (default 20)

No output schema declared.

No examples provided.

paper_replay ~261

Replay a strategy on the recorded tape and return the report: trades, win rate with its 95 % lower bound, costs, and a verdict. GATE NOT CLEARED is the usual outcome of a short tape, and it means the tape is too short to tell, not that the strategy is bad; run paper_record again over days. A replay never proves that a real order will win: it is what the recorded past would have given, fees and funding counted, and nothing is signed.

NameTypeReqDescription
coinsstring–Only these markets of the tape, comma separated (BTC,ETH)
fromstring–The start: a date, a timestamp in milliseconds, or a duration back from now (3d, 6h)
strategyobjectyesThe strategy, as a JSON object of schema version 1: version, name (lower-case letters, digits and dashes), an optional comment, when (the conditions) and order (side, sizeUsd, leverage, entry, tp, sl…
tostring–The end, in the same forms as from

No output schema declared.

No examples provided.

paper_status ~22

Equity, positions and fees of the simulation account, at live marks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

perps_balance ~100

Equity and withdrawable margin, per dex (the simulation account's with paper: true).

NameTypeReqDescription
addressstring–Another account to read (0x...); omit for the vault account
all_dexesboolean–Every dex the account is funded on
dexstring–A HIP-3 dex by name, in lower case (omit for the main dex)
paperboolean–On the simulation account

No output schema declared.

No examples provided.

perps_cancel ~108

Cancel an open order. Runs only with confirm: true and the quote_id the same call without confirm returned; without them, signs nothing.

NameTypeReqDescription
confirmboolean–The user's agreement to this order. Without it nothing is signed.
order_idintegeryesThe order id (perps_orders)
quote_idstring–The quote_id of the quote this confirms, as the same call without confirm returned it.
symbolstringyesThe market of the order

No output schema declared.

No examples provided.

perps_close ~182

Close a position (reduce-only, at market), or every one with all: true. Without confirm, returns what would close and a quote_id, and signs nothing. Closing is always allowed by the policy.

NameTypeReqDescription
allboolean–Every open position (instead of symbol)
confirmboolean–The user's agreement to this order. Without it nothing is signed.
max_slippage_bpsinteger–The worst price accepted, in basis points (default 300)
paperboolean–On the simulation account
quote_idstring–The quote_id of the quote this confirms, as the same call without confirm returned it.
sizestring–Part of the position, in the base asset, never more than it holds (the whole position when absent)
symbolstring–The market to close

No output schema declared.

No examples provided.

perps_deposit ~72

Deposit USDC from Arbitrum to Hyperliquid. Signed by the user's own wallet (Locker Vault, their browser extension or their mobile wallet): this tool signs nothing and returns the command the user types in their own terminal.

NameTypeReqDescription
amountstringyesUSDC to bring from Arbitrum One

No output schema declared.

No examples provided.

perps_markets ~114

Markets by 24 h volume: mark price, 24 h change, funding, open interest, maximum leverage; halted ones marked.

NameTypeReqDescription
all_dexesboolean–Every dex the account is funded on
dexstring–A HIP-3 dex by name, in lower case (omit for the main dex)
limitinteger–How many markets, largest 24 h volume first (default 25)
searchstring–Only the markets whose name holds this text

No output schema declared.

No examples provided.

perps_modify ~138

Change the leverage of a market, or set TP/SL on an open position. Runs only with confirm: true and the quote_id the same call without confirm returned; without them, signs nothing.

NameTypeReqDescription
confirmboolean–The user's agreement to this order. Without it nothing is signed.
leverageinteger–A new leverage (within the policy)
quote_idstring–The quote_id of the quote this confirms, as the same call without confirm returned it.
slstring–A stop-loss price
symbolstringyesThe market
tpstring–A take-profit price

No output schema declared.

No examples provided.

perps_open ~437

Open or add to a position. Without confirm, returns the quote, the local policy check and a quote_id, and signs nothing. With confirm: true and that quote_id, the guardian rebuilds the order, checks the policy again and signs it with the agent key.

NameTypeReqDescription
confirmboolean–The user's agreement to this order. Without it nothing is signed.
leverageintegeryesThe leverage, e.g. 3
limit_pxstring–The limit price, with type limit
marginstring–cross or isolated: the margin the leverage is set in (default: the position's, or the market's; a market that takes isolated only refuses cross). The leverage is set for the whole market
max_slippage_bpsinteger–The worst price accepted, in basis points from the mid (default 300)
paperboolean–On the simulation account
quote_idstring–The quote_id of the quote this confirms, as the same call without confirm returned it.
reduce_onlyboolean–Only reduce the position held, the side the other way: no leverage set, no margin taken, always allowed by the policy as a close
sidestringyeslong or short
sizestringyesThe size in the base asset, e.g. 0.01
slstring–A stop-loss price
symbolstringyesThe market, e.g. BTC, ETH, xyz:GOLD
tifstring–With type limit: gtc (default) rests until cancelled, ioc fills what it can at once and cancels the rest, alo is posted to the book only and refused if it would fill at once
tpstring–A take-profit price
trigger_pxstring–The entry trigger, with type trigger: a long above the price, a short below; no tp or sl with it
typestring–market (default), limit, or trigger (a market order once the price reaches trigger_px)

No output schema declared.

No examples provided.

perps_orders ~119

Open orders, triggers included (the simulation account's with paper: true: its entry triggers waiting for their price, judged on the mark first, one reached filled and said under fired).

NameTypeReqDescription
addressstring–Another account to read (0x...); omit for the vault account
all_dexesboolean–Every dex the account is funded on
dexstring–A HIP-3 dex by name, in lower case (omit for the main dex)
paperboolean–On the simulation account

No output schema declared.

No examples provided.

perps_positions ~106

Open positions (the simulation account's with paper: true, or when simulation mode is on and no address is given).

NameTypeReqDescription
addressstring–Another account to read (0x...); omit for the vault account
all_dexesboolean–Every dex the account is funded on
dexstring–A HIP-3 dex by name, in lower case (omit for the main dex)
paperboolean–On the simulation account

No output schema declared.

No examples provided.

perps_quote ~362

What an order would cost before anything is signed: entry and worst price on the live book, fees as one total, liquidation estimate, Hyperliquid's $10 minimum.

NameTypeReqDescription
leverageintegeryesThe leverage, e.g. 3
limit_pxstring–The limit price, with type limit
marginstring–cross or isolated: the margin the leverage is set in (default: the position's, or the market's; a market that takes isolated only refuses cross). The leverage is set for the whole market
max_slippage_bpsinteger–The worst price accepted, in basis points from the mid (default 300)
reduce_onlyboolean–Only reduce the position held, the side the other way: no leverage set, no margin taken, always allowed by the policy as a close
sidestringyeslong or short
sizestringyesThe size in the base asset, e.g. 0.01
slstring–A stop-loss price
symbolstringyesThe market, e.g. BTC, ETH, xyz:GOLD
tifstring–With type limit: gtc (default) rests until cancelled, ioc fills what it can at once and cancels the rest, alo is posted to the book only and refused if it would fill at once
tpstring–A take-profit price
trigger_pxstring–The entry trigger, with type trigger: a long above the price, a short below; no tp or sl with it
typestring–market (default), limit, or trigger (a market order once the price reaches trigger_px)

No output schema declared.

No examples provided.

perps_ranges ~133

Which markets are in a range now, over the last 4 hours: range width, volatility, their ratio (ranginess), a score from 0 to 10 (0 outside 0.5 to 5 % wide), support and resistance. The markets whose candles fail are skipped and counted.

NameTypeReqDescription
all_dexesboolean–Every dex the account is funded on
dexstring–A HIP-3 dex by name, in lower case (omit for the main dex)
limitinteger–How many markets to scan, by 24 h volume (default 20)

No output schema declared.

No examples provided.

perps_regime ~116

The regime of a market, read on its 1 h, 4 h and 5 m candles: strong bull, weak bull, range, weak bear or strong bear with its trend score, the EMA stack, the structure (higher highs and lows), RSI 14 and 6, ATR and whether volatility expands, volume, and how long the regime has held. It tells a trending market from one in a range.

NameTypeReqDescription
symbolstringyesThe market, e.g. BTC, ETH, xyz:GOLD

No output schema declared.

No examples provided.

perps_transfer ~105

Move USDC margin between the main dex and a HIP-3 dex of the account. Signed by the user's own wallet (Locker Vault, their browser extension or their mobile wallet): this tool signs nothing and returns the command the user types.

NameTypeReqDescription
amountstringyesUSDC to move
from_dexstring–The dex to move from (default main)
to_dexstringyesThe dex to move to (main for the main dex)

No output schema declared.

No examples provided.

perps_venues ~23

The perps venues this wallet trades on (Hyperliquid).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

perps_withdraw ~94

Withdraw USDC to Arbitrum. Signed by the user's own wallet (Locker Vault, their browser extension or their mobile wallet): this tool signs nothing and returns the command the user types in their own terminal. The agent key cannot withdraw (Hyperliquid refuses it).

NameTypeReqDescription
amountstringyesUSDC to withdraw to Arbitrum
destinationstring–Another address (omit for the vault account)

No output schema declared.

No examples provided.

pilot_status ~53

The pilot that trades on its own in the guardian: running and when it thinks next, paused and why, or ended. Read only: no tool arms, stops or resumes it; the user does, in their terminal.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

policy_show ~41

The limits every order is checked against: size per order, leverage, markets, orders per day, risk:reward, expiry and the bounds set on this computer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

status ~24

Account, agent, guardian (locked or unlocked) and mode, at a glance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wallet_address ~31

The account the agent trades for, and how it signs: Locker Vault, a browser extension or a mobile wallet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wallet_balances ~41

ETH and USDC on Arbitrum, margin and spot on Hyperliquid.

NameTypeReqDescription
addressstring–Another account (omit for the vault account)

No output schema declared.

No examples provided.

Install

How do I install the Locker Protocol Agentic MCP server?

Locker Protocol Agentic runs locally as an npm package, launched with npx -y @locker-protocol/agent-wallet-hyperliquid-trader-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 · @locker-protocol/agent-wallet-hyperliquid-trader-mcp

# add to Claude Code
claude mcp add locker-protocol-agentic -- npx -y @locker-protocol/agent-wallet-hyperliquid-trader-mcp
Common questions

What is the Locker Protocol Agentic MCP server?

Locker Protocol Agentic is an MCP server listed in the public MCP registry as io.github.locker-protocol/agentic. Hyperliquid perps for AI agents. The agent trades; the keys stay offline in Locker Vault. This page covers its npm package (@locker-protocol/agent-wallet-hyperliquid-trader-mcp).

Is the Locker Protocol Agentic MCP server safe to use?

Locker Protocol Agentic scores 65 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 18 October 2026. It declares no install or post-install scripts. 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.

What tools does the Locker Protocol Agentic MCP server expose?

Locker Protocol Agentic exposes 42 tools: perps_venues, perps_markets, perps_quote, perps_positions, perps_balance, and 37 more. Their descriptions and schemas cost roughly 4,238 tokens of context every time the server is loaded.

Is the Locker Protocol Agentic MCP server still maintained?

Locker Protocol Agentic is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.