Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
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.
93/100
trust score
8
downloads a day
local
runs on your machine
225
downloads in 30d
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 — add it to Claude Code
claude mcp add --scope user wikey-wallet-mcp '--' npx -y wikey-wallet-mcp
# 2 — ask your agent for something these tools do
# wallet_getting_started, wallet_chain_info, wallet_balance and 47 more
Wikey Wallet costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
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. Its scan result is on the Security tab — 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. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user wikey-wallet-mcp '--' npx -y wikey-wallet-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
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
50 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 \
No parameter schema on file.
Get Omnistar chain ID and latest block height.
No parameter schema on file.
Get OST balance directly held by an address (use for gas/funding checks).
No parameter schema on file.
Get all OST balances for an address.
No parameter schema on file.
Get account number and sequence for an address.
No parameter schema on file.
Take a snapshot of the profile
No parameter schema on file.
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:
No parameter schema on file.
Explicit pagination over a (safe, class) in a cached snapshot. Returns { rows, offset, limit, returned, total, truncated }. Supports fields:[...]|
No parameter schema on file.
Get on-chain profile (pubkey, policies, linked safes). Uses config address when omitted.
No parameter schema on file.
Get the full asset portfolio of an account
No parameter schema on file.
List every signing key on this machine with what the chain says about it: { address, name?, funded?, safes[] }. This is the answer to \
No parameter schema on file.
List all key IDs in the signing-server.
No parameter schema on file.
Get details for a specific key ID.
No parameter schema on file.
Generate a new keypair in the signing-server. Returns { result, fundingUrl, next }:
No parameter schema on file.
Show the full wallet-cli configuration (read-only).
No parameter schema on file.
Get a single config value by dot-path key (read-only, e.g. user.address).
No parameter schema on file.
Initialize wallet-cli configuration with defaults.
No parameter schema on file.
Reset wallet-cli configuration to defaults.
No parameter schema on file.
Show the path to the wallet-cli config file.
No parameter schema on file.
Recover a wedged SSP session in place — call this when wallet_session_status reports wedged:true (or a signing tool fails with
No parameter schema on file.
Create a safe + profile on-chain with a username. Takes ~30s to validate after broadcast.
No parameter schema on file.
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
No parameter schema on file.
Will this transfer succeed? Read-only pre-flight for wallet_tx_create_transaction — call it BEFORE sending, and ALWAYS when the user says \
No parameter schema on file.
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 \
No parameter schema on file.
Vote on an on-chain object. signature is the Omnistar tx hash (the SIGNATURE field from wallet_snapshot_query / wallet_profile).
No parameter schema on file.
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
No parameter schema on file.
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
No parameter schema on file.
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
No parameter schema on file.
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
No parameter schema on file.
Soft-delete a policy from a safe. Data remains on-chain. policyId is the policy-object id from wallet_snapshot_query (filter {class:
No parameter schema on file.
Remove a user from a SAFE
No parameter schema on file.
Configure notifications. Returns a token credential — display to the user ONCE with an explanation, then drop it. At least one channel field required.
No parameter schema on file.
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.
No parameter schema on file.
Forget the local gateway target + enrolled credential so the next register starts clean. Does not delete the passkey on the remote gateway. No signing.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Wikey Wallet or to call it, 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: —
ATrust score 93 / 100
Release 1.4.0 · scanned 15 Oct 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
Findings9 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digeste69e10d4c476724e7e0bc445f8d15afb076daebbba38cb00e74868697e5c6096
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 (50 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_resolve_recipient | no tags | |
| wallet_tx_edit_helpers | no tags | |
| wallet_notification_configure | external-sink | external-sink: parameter "webhook" |
| wallet_notification_pull | no tags | |
| wallet_notification_migrate_trustors | no tags | |
| 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 |
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 digeste69e10d4c476724e
Scanned2026-10-15
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.4.0. Pin a release below and the command asks for exactly that one.
1.4.0
3 Sep 2026
latestNo release note was published with this version.
1.3.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Wikey Wallet can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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 a signed-in account that does not publish it, and nothing else.