MCP server that gives coding agents typed 0xArchive market data tools across Hyperliquid (perps, HIP-3, HIP-4, spot) and Lighter.xyz
Free
Nothing to run from here
Wikey Wallet is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Wikey Wallet MCP — a self-hosted, zero-custody MCP stdio server that exposes the Omnistar wallet/signing stack to a client's own agent through a typed, enforceable tool boundary.
Quickstart
# 1 — run it from where its publisher ships it
npx -y wikey-wallet-mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> Wikey Wallet MCP — a self-hosted, zero-custody MCP stdio server that exposes the Omnistar wallet/signing stack to a client's own agent
Publishernot claimed
BIAll 1 server
bit2safe1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Wikey Wallet as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add wikey-wallet-mcp -- npx -y wikey-wallet-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
34 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
START HERE. Read-only onboarding guide that answers \
Takes no parameters.
Example callreturns →
Get Omnistar chain ID and latest block height.
Takes no parameters.
Example callreturns →
Get OST balance directly held by an address (use for gas/funding checks).
Takes no parameters.
Example callreturns →
Get all OST balances for an address.
Takes no parameters.
Example callreturns →
Get account number and sequence for an address.
Takes no parameters.
Example callreturns →
Take a snapshot of the profile
Takes no parameters.
Example callreturns →
Query rows from a cached snapshot (by snapshotId from wallet_snapshot). By DEFAULT each row is a summary projection (safe, group, groupName, class, id, isDeleted, parentGroup, SIGNATURE) — NOT the full object. Request payload keys with fields:[...] or fields:
Takes no parameters.
Example callreturns →
Explicit pagination over a (safe, class) in a cached snapshot. Returns { rows, offset, limit, returned, total, truncated }. Supports fields:[...]|
Takes no parameters.
Example callreturns →
Get on-chain profile (pubkey, policies, linked safes). Uses config address when omitted.
Takes no parameters.
Example callreturns →
Get the full asset portfolio of an account
Takes no parameters.
Example callreturns →
List every signing key on this machine with what the chain says about it: { address, name?, funded?, safes[] }. This is the answer to \
Takes no parameters.
Example callreturns →
List all key IDs in the signing-server.
Takes no parameters.
Example callreturns →
Get details for a specific key ID.
Takes no parameters.
Example callreturns →
Generate a new keypair in the signing-server. Returns { result, fundingUrl, next }:
Takes no parameters.
Example callreturns →
Show the full wallet-cli configuration (read-only).
Takes no parameters.
Example callreturns →
Get a single config value by dot-path key (read-only, e.g. user.address).
Takes no parameters.
Example callreturns →
Initialize wallet-cli configuration with defaults.
Takes no parameters.
Example callreturns →
Reset wallet-cli configuration to defaults.
Takes no parameters.
Example callreturns →
Show the path to the wallet-cli config file.
Takes no parameters.
Example callreturns →
Recover a wedged SSP session in place — call this when wallet_session_status reports wedged:true (or a signing tool fails with
Takes no parameters.
Example callreturns →
Create a safe + profile on-chain with a username. Takes ~30s to validate after broadcast.
Takes no parameters.
Example callreturns →
Send OST directly between key addresses (not safe funds). Use for gas funding. The gas for this transaction is paid in the OST being sent, so the sender
Takes no parameters.
Example callreturns →
Will this transfer succeed? Read-only pre-flight for wallet_tx_create_transaction — call it BEFORE sending, and ALWAYS when the user says \
Takes no parameters.
Example callreturns →
Move assets out of a safe. Use this (not wallet_tx_send) when the safe holds the funds. amount must be in SMALLEST units (display value × smallCoin from wallet_assets). THE NETWORK FEE IS DEDUCTED FROM THE SAME BALANCE, so the full balance is NEVER sendable — a request to send \
Takes no parameters.
Example callreturns →
Vote on an on-chain object. signature is the Omnistar tx hash (the SIGNATURE field from wallet_snapshot_query / wallet_profile).
Takes no parameters.
Example callreturns →
Request account recovery for an existing username (for a user who lost their key). Signs with the NEW key and references the original account by username (wallet-cli requires --username). Pass
Takes no parameters.
Example callreturns →
Approve a recovery request as a helper. If a friend sent you a recovery deeplink (https://open.wikey.io/accountRecover?t=recover&pk=<newAddress>&tn=<accountName>), just pass it as
Takes no parameters.
Example callreturns →
Create a policy on a safe. Valid applyOn values: group, user, transaction, policy, profile (comma-separated for multiple). MIXING RULE: amount and symbols conditions ONLY available when applyOn is exactly
Takes no parameters.
Example callreturns →
Edit an existing policy on a safe. Same applyOn and conditions rules as wallet_tx_create_policy. MIXING RULE: amount and symbols only when applyOn is exactly
Takes no parameters.
Example callreturns →
Soft-delete a policy from a safe. Data remains on-chain. policyId is the policy-object id from wallet_snapshot_query (filter {class:
Takes no parameters.
Example callreturns →
Remove a user from a SAFE
Takes no parameters.
Example callreturns →
Configure notifications. Returns a token credential — display to the user ONCE with an explanation, then drop it. At least one channel field required.
Takes no parameters.
Example callreturns →
Show the current gateway target and the enrolled passkey credential (client secret masked). Reports the resolved default-key account and whether the stored credential matches the active target. No network, no signing.
Takes no parameters.
Example callreturns →
Forget the local gateway target + enrolled credential so the next register starts clean. Does not delete the passkey on the remote gateway. No signing.
Takes no parameters.
Example callreturns →
Standardmost installed
$15 / month
- 12,000 calls a month, included
- 144 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Scale
$59 / month
- 100,000 calls a month, included
- 1,200 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $15 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 93 / 100
Release 1.3.1 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 9 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestee67d03fa0fd62eb4d75f24d3ffc14eeeccaf1cc98033121598c36c1b7e132be
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (49 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| wallet_getting_started | no tags | |
| wallet_chain_info | no tags | |
| wallet_balance | no tags | |
| wallet_balances | no tags | |
| wallet_account | no tags | |
| wallet_snapshot | no tags | |
| wallet_snapshot_query | no tags | |
| wallet_snapshot_page | no tags | |
| wallet_snapshot_object | no tags | |
| wallet_profile | no tags | |
| wallet_assets | no tags | |
| wallet_accounts | no tags | |
| wallet_keys_list | no tags | |
| wallet_keys_get | no tags | |
| wallet_keys_create | no tags | |
| wallet_config_show | no tags | |
| wallet_config_get | no tags | |
| wallet_config_set | no tags | |
| wallet_config_init | no tags | |
| wallet_config_reset | no tags | |
| wallet_config_path | no tags | |
| wallet_session_status | no tags | |
| wallet_session_recover | no tags | |
| wallet_tx_create_safe | no tags | |
| wallet_onboard_sponsor | no tags | |
| wallet_tx_send | no tags | |
| wallet_tx_check | no tags | |
| wallet_tx_create_transaction | no tags | |
| wallet_tx_vote | no tags | |
| wallet_tx_request_recovery | no tags | |
| wallet_tx_approve_recovery | no tags | |
| wallet_tx_create_policy | no tags | |
| wallet_tx_edit_policy | no tags | |
| wallet_tx_delete_policy | no tags | |
| wallet_tx_create_user | no tags | |
| wallet_tx_delete_user | no tags | |
| wallet_recovery_helpers | no tags | |
| wallet_resolve_name | no tags | |
| wallet_tx_edit_helpers | no tags | |
| wallet_notification_configure | external-sink | |
| wallet_gateway_register | no tags | |
| wallet_gateway_login | no tags | |
| wallet_gateway_api_call | no tags | |
| wallet_gateway_mcp_call | no tags | |
| wallet_gateway_status | no tags | |
| wallet_uninstall | no tags | |
| wallet_gateway_logout | no tags | |
| getting-started | no tags | |
| help | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestee67d03fa0fd62eb
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.3.1 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.3.1
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Wikey Wallet in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.