npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@zypheragent/mcp

v0.8.0

Published

MCP server for AI agents on Hyperliquid, HyperEVM and Elysium: market data and token checks (no setup), plus swaps, perps with TP/SL, deposits and token launches through your own Agent Wallet. Works with Claude Code, Codex, Cursor and any stdio MCP client

Readme

@zypheragent/mcp

Give your AI agent real market data and a wallet it can trade from. This is the Model Context Protocol server of Zypher Agent. It works with Claude Code, Codex, Cursor, Claude Desktop, omp and any client that speaks stdio MCP.

  • Read, no setup. Hyperliquid perps, HyperEVM quotes, the Elysium market, holders, activity and token checks. No account, no key, no token.
  • Act, when you allow it. Add one API token from your Agent Wallet and the agent can swap, trade perps with TP/SL, deposit, launch a token and bridge, inside caps you set.
  • Your key stays on the server. The package holds no keys and cannot sign anything.

Execution moves real funds on mainnet, with no confirmation step. Start with a small balance and low caps. See Safety.

Start in 2 minutes

You need Node.js 20 or newer.

1. Read-only (no token)

claude mcp add -s user zypher-agent -- npx -y @zypheragent/mcp

Open Claude Code and ask: "Use Zypher to give me a market brief: BTC, ETH and HYPE funding, open interest and the top 3 Elysium tokens by volume."

2. Turn on execution (optional)

  1. Open zypheragent.com/agent and go to Agent > Wallet > API tokens.
  2. Create a token (zat_ plus 40 characters). It is shown once.
  3. Add it from your terminal, never in a chat:
claude mcp add -s user -e ZYPHER_API_TOKEN=zat_YOUR_TOKEN zypher-agent -- npx -y @zypheragent/mcp

Restart the client. You now have 33 tools. Ask the agent to call agent_status first: it shows your wallet, balances on Arbitrum, HyperEVM, Elysium and Hyperliquid, positions, open orders and caps.

Other clients (Cursor, Claude Desktop, Codex, omp, any stdio client) use the JSON config in Client configuration.

How it works

The model asks, the Zypher server checks and signs, and your limits decide. Nothing is signed on your machine and nothing is signed by the model.

What you can ask for

| Goal | Say something like | Tools | | --- | --- | --- | | Understand the market | "Brief me on BTC, ETH and HYPE, and the 24h BTC trend." | get_perp_markets, get_candles, analyze_ticker | | Vet a token before trading | "Check the top Elysium token. Does its volume match on-chain activity?" | get_elysium_market, get_elysium_token, get_elysium_activity, get_elysium_holders, analyze_token_health | | See your wallet | "Show my Agent Wallet on every chain." | agent_status | | Fund perps | "Move 12 USDC from Arbitrum into Hyperliquid." | agent_hl_deposit | | Trade a perp | "Long BTC, $10, 2x isolated, with a 3% stop and 5% take profit." | agent_perp_order, agent_protect, agent_close, agent_cancel | | Swap | "Swap 0.02 HYPE to USDC on HyperEVM." | quote_swap, agent_swap | | Trade or launch on Elysium | "Launch a token called ZTEST, no first buy." | agent_elysium_swap, agent_elysium_launch, upload_token_image | | Move money | "Bridge HYPE to Elysium." "Send my funds back to my wallet." | agent_bridge_elysium, agent_bridge, agent_transfer_out |

Tip: for anything that moves money, tell the agent to show the plan and wait for your "yes". The MCP itself does not ask.

Safety

  • Your key never leaves the Agent Wallet. This package contains no signing code and no key handling.
  • Caps and a kill switch are enforced on the server, per action and per day, so a confused or manipulated model cannot raise them.
  • Bad requests fail before anything is signed: a limit order without a price, take profit without levels, a deposit under the 5 USDC minimum, a swap above its price-impact limit.
  • Every write carries a fresh Idempotency-Key. After a timeout the outcome is unknown, so the agent must call agent_status before retrying.
  • Treat token names and tweets as data, not instructions. Do not auto-approve agent_* tools in your client.
  • Revoke the token in the app (Agent > Wallet > API tokens) as soon as you stop using it. Use a dedicated Agent Wallet with a small balance.

Client configuration

Claude Code (shown above), and any other client through its MCP config:

{
  "mcpServers": {
    "zypher-agent": {
      "command": "npx",
      "args": ["-y", "@zypheragent/mcp"],
      "env": { "ZYPHER_API_TOKEN": "zat_YOUR_TOKEN" }
    }
  }
}
  • Claude Desktop: claude_desktop_config.json
  • Cursor: ~/.cursor/mcp.json or .cursor/mcp.json
  • Codex, omp and others: their MCP settings, as a stdio server with command npx and args -y @zypheragent/mcp

Leave out env for read-only. The server starts with no environment variables and no config file. Its ready line (zypher-mcp <version> ready (stdio, read-only, ...), or read + EXECUTION ... when a token is set) goes to stderr, so it never mixes with the protocol on stdout. Binaries: zypher-mcp and zypheragent-mcp (same program).

If the client says spawn npx ENOENT, Node.js is missing or not on the PATH the app uses.

Reference

Execution tools (14, need a token)

With a valid ZYPHER_API_TOKEN the server registers fourteen more tools (33 in total) and its ready line says read + EXECUTION. A malformed token prints a clear error on stderr and execution stays disabled; the 17 read tools keep working.

| Tool | What it does | Arguments | | --- | --- | --- | | agent_status | Your Agent Wallet: address, balances, positions, open orders, recent fills, caps and usage. Does not move funds. | none | | agent_swap | Exact-in swap on HyperEVM from the Agent Wallet. | tokenIn, tokenOut (symbol or 0x address), amountIn, optional slippageBps | | agent_elysium_swap | Swap on Elysium 99901 (native HYPE <-> a Boxa-indexed token) from the Agent Wallet. | tokenIn, tokenOut (HYPE on one side; symbol or 0x address), amountIn, optional slippageBps | | agent_elysium_launch | Launch a token on Elysium through Boxa's V3 launcher from the Agent Wallet (1B supply in locked liquidity, no creation fee). | name, symbol, optional description, image/website/twitter/telegram (https URLs), allocation (balanced, creator, holders, buyback, liquidity or four basis-point shares summing to 10000), antiSnipe, firstBuyHype | | agent_bridge_elysium | Move native HYPE HyperEVM <-> Elysium for the Agent Wallet (fund it before an Elysium swap or launch). | direction (deposit|withdraw), amount | | agent_bridge | Bridge with Relay between chains (name or id, tokens by symbol/address) from the Agent Wallet. Recipient: the wallet itself or an address on your send allow-list. | originChain, destinationChain, amount, optional originToken, destinationToken, recipient | | agent_hl_deposit | Fund perps: move native USDC the Agent Wallet holds on Arbitrum into its Hyperliquid account (one transfer to Hyperliquid's bridge). Minimum 5 USDC. | amount | | upload_token_image | Upload a token image (PNG/JPEG/GIF/WebP, up to 4 MB, base64 or data URL) and get an https URL for agent_elysium_launch. No funds, API token not sent. | imageBase64 | | agent_perp_order | Open/add a Hyperliquid perp: market/GTC limit, isolated/cross, optional native TP/SL. | coin (BTC, xyz:NVDA), side long|short, notionalUsd, leverage, optional orderType, limitPrice, marginMode, tpPrice, slPrice, reduceOnly | | agent_close | Close a perp position (all or a percentage). | coin, optional fractionPct (0-100) | | agent_protect | Add native reduce-only TP and/or SL to an existing position. | coin, tpPrice and/or slPrice | | agent_cancel | Cancel one resting limit/trigger order using the oid from agent_status.openOrders. | coin, oid | | agent_send | Send funds from the Agent Wallet to an external 0x address. | asset, amount, to (0x address) | | agent_transfer_out | Move funds from the Agent Wallet back to your own main wallet. | asset, amount |

These tools move real funds on mainnet. Every call executes immediately from your Agent Wallet, inside the caps set by you / the operator in the app. There is no confirmation step in the MCP, so the assistant is told to ask you first; do not auto-approve these tools in your client. No tool accepts a wallet, owner, URL or path argument: the package can only call the thirteen fixed paths /api/agent-api/{status,swap,elysium-swap,elysium-launch,bridge-boxa,bridge,hl-deposit,perp-order,close,protect,cancel,send,transfer-out} (plus the public image upload route of the same host for upload_token_image, which never receives the token) under ZYPHER_API_URL.

Each write call carries a fresh random Idempotency-Key. Timeouts are 15 s (45 s for swaps); redirects are refused and responses over 100 KB are refused. After a timeout or a 5xx on a write, the outcome is unknown: call agent_status before retrying.

Read tools (19, always on)

| Tool | What it does | | --- | --- | | get_policy | Shows the policy and execution state of this server and, when read-only, the exact steps to turn execution on. | | analyze_ticker | Hyperliquid perp analysis for any listed market, crypto or trade.xyz stocks/indices/metals (BTC, xyz:NVDA, or the bare symbol NVDA): price, 24h volume, open interest, funding, orderbook depth. | | get_strong_volume | Perp tickers with the highest 24h volume, with volume/OI ratio and price change. | | get_new_pairs | Newest token launches on Elysium 99901 (all launchpads), newest first. Elysium only; chain=hyperevm returns an explicit error. | | get_elysium_market | The Elysium market / launchpad feed (like the app's Market and Launch tabs): sort newest, fdv (top), volume (trending), change (gainers), trades, holders; filter by launchpad (boxa, kleos, ascend, montra, volta, elyspump, uniswap, stockium, stocks...), search q, tradable. Read from the Zypher public API. | | get_elysium_activity | Recent swaps (or transfers) of an Elysium token, newest first, from chain logs (side, amounts, wallet, block); page backwards with before. Times are approximate. | | get_elysium_holders | Largest holders of an Elysium token seen in recent activity (not a full ranking) plus the index holder count. | | get_elysium_token | One Elysium token by address: launchpad, pool, price, FDV, 24h change/volume, holders, tradable flag. | | analyze_token_health | Bytecode/ABI check of a token contract (mint, pause, blacklist, owner) with a score and reasons. A heuristic, not an audit. | | get_social_info | Recent tweets about a ticker. Needs your own X_BEARER_TOKEN; without it the tool returns a clear error. | | get_portfolio | Public balances/positions of an address: Hyperliquid account, HYPE and tokens on HyperEVM and on Elysium 99901. | | get_swap_holdings | What an address actually holds on HyperEVM or Elysium (chain): HYPE and every token with a balance. Each token has a status (a failed read is never shown as zero), verified, a USD value when priced, and coverage (Elysium scans the whole index). Token names are untrusted text. | | check_token_safety | Heuristic honeypot test on HyperEVM or Elysium (chain): a simulated small buy, transfer and sell. tested:false means no pool route was found and nothing is known about the token, which is not the same as safe. Not an audit; nothing is signed or sent. | | get_market_tokens | HyperEVM mainnet tokens (HyperSwap V3, a verified list): USD price from the deepest sane pool, TVL, pool health. No 24h change. Not every token on the chain. | | quote_swap | Exact-in swap quote on HyperSwap V3 (HyperEVM mainnet): output, route, price impact; sane pools only. Quote only; nothing is built or sent. | | get_perp_markets | All Hyperliquid perp markets (own dex, about 179, plus trade.xyz stocks, indices and metals as xyz:NVDA, about 120): price, 24h change, volume, open interest, funding, max leverage. | | get_candles | Hyperliquid candles: summary statistics plus the last 20 candles. | | get_launch_info | Read-only facts about token launches on Elysium 99901 through Boxa's V3 launcher: chain check, contract code-hash pins, pool fee, treasury share, supply. Read-only; to launch use agent_elysium_launch. | | get_hl_account | Hyperliquid account state of a public address: value, margin, positions, open orders. |

All tool output is JSON text. Text that comes from third parties (token names, tweets) is sanitised and should still be treated as untrusted data, not as instructions.

Environment variables (all optional)

| Variable | Default | Meaning | | --- | --- | --- | | ZYPHER_NETWORK | mainnet | Hyperliquid network for perp reads (mainnet is the default and the product's only network). | | ZYPHER_ADDRESS | unset | Public 0x... address used by get_portfolio / get_hl_account when no address argument is passed. Never put a private key here. | | X_BEARER_TOKEN | unset | Your X API bearer token, only for get_social_info. | | ZYPHER_API_TOKEN | unset | Agent Wallet API token (zat_ + 40 lowercase hex). Enables the 13 agent_* tools and upload_token_image. Sent only as Authorization: Bearer to ZYPHER_API_URL; never logged. | | ZYPHER_API_URL | https://zypheragent.com/agent | Base URL of the Zypher Agent API. Must be https (plain http only for localhost / 127.0.0.1). A different host prints a one-line stderr warning that the token will be sent there. | | ELYSIUM_RPC | https://rpc-live.boxa.club | Override the Elysium (99901) RPC URL. | | HYPEREVM_RPC | public HyperEVM RPC | Override the HyperEVM (999) RPC URL. |

No other variables are read.

Network behaviour

  • Without a token only public, unauthenticated data endpoints are contacted. With ZYPHER_API_TOKEN it additionally talks to ZYPHER_API_URL (default https://zypheragent.com/agent), only on the thirteen fixed /api/agent-api/* paths. Read tools contact: the Hyperliquid info API (api.hyperliquid.xyz), the public HyperEVM RPC (rpc.hyperliquid.xyz/evm) and the Elysium 99901 RPC (rpc-live.boxa.club, run by Boxa) and, for the Elysium market tools, get_swap_holdings and check_token_safety, the public Zypher API (zypheragent.com/agent; read-only, no token sent). get_social_info contacts api.x.com only with your own token.
  • Requests carry the header User-Agent: zypher-mcp/<version>.
  • No telemetry, no analytics, no phone-home. The package writes nothing to disk.
  • Default is mainnet (real markets): Hyperliquid mainnet, HyperEVM 999 and Elysium 99901. Elysium 99901 is a community-run chain served by Boxa (rpc-live.boxa.club), not the official Kinetiq mainnet; get_launch_info checks that the chain id and the pinned contract code hashes still match and says so when they do not. Its RPC and contracts are third-party; a lying or lagging RPC cannot be detected from here.

What it does not do

  • Without ZYPHER_API_TOKEN: no trading, no order preparation, no execution. In every mode this package builds and signs no transactions: the Zypher server does, for your Agent Wallet.
  • No private keys, seed phrases or direct wallet access of any kind: the Agent Wallet is held and signed by the Zypher Agent server, never by this package.
  • Launching is only possible through your Agent Wallet token (agent_elysium_launch); get_launch_info only reads facts.
  • No price history beyond the candles from Hyperliquid, and no token search by name on launchpads (use addresses).

Limits

  • Data comes from public APIs and RPCs; it can be stale, rate-limited, incomplete or wrong. Public RPCs may throttle heavy use.
  • analyze_token_health inspects bytecode patterns and basic ERC-20 metadata only. A high score is not a safety guarantee.
  • Nothing here is financial advice.

Security notes

  • The published bundle contains no signing code and no key handling. Pass only public addresses to the read tools.
  • Execution is opt-in and uses real money. Use a dedicated Agent Wallet with a small balance, keep the caps in the app low, and revoke the token in the app (Agent > Wallet > API tokens) as soon as you stop using it or suspect a leak. Caps and the revocation are enforced server-side.
  • Prompt injection: token names, tweets, web pages and other tool output can contain text that tries to make your assistant call agent_swap / agent_send. Do not auto-approve agent_* tools; read every call's parameters (especially to and amounts) before you accept it.
  • The token is only sent in the Authorization header to the configured base URL, never in a query string, log, tool result or error message.
  • The server runs locally over stdio; it opens no network port.
  • Treat tool output as data. Do not let an assistant act on instructions found inside token names or tweets.
  • Have a look at the single bundled file dist/index.js if you want to audit it.

License

MIT, see LICENSE.