Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Highwire 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.
99/100
trust score
30
tools declared
local
or remote
—
downloads a day
What it does
Trade, launch and research higher.fun coins on Solana, from any AI agent. Unsigned or policy-signed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user highwire-mcp '--' npx -y highwire-mcp
# 2 — ask your agent for something these tools do
# build_transfer, get_signer_status, execute_trade and 27 more
Highwire costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HIAll 1 server
highwire1 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 can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
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 highwire-mcp '--' npx -y highwire-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://highwire.fun/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http highwire-mcp https://highwire.fun/mcpFree 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 asks of you
Nothing is required, but it can take HIGHWIRE_CLUSTER (mainnet (default) or devnet), SOLANA_RPC_URL (Your Solana RPC URL; defaults to the public one), HIGHWIRE_KEYPAIR_PATH (A keypair file, to turn on the local signer (it signs only inside your policy)) if you want to set them.
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
30 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Build an unsigned transaction that sends SOL, or a higher.fun coin, from a wallet to another wallet. It has no
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | yes | — |
The local signer's wallet, whether it's live or dry-run only, the user's policy (limits, allowed actions, coins
No parameter schema on file.
Build a buy or sell exactly as build_trade does, for the local signer's wallet, then sign and send it if the user's
No parameter schema on file.
Launch a coin exactly as build_launch builds it, from the local signer's wallet, then sign and send it if the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image_path | string | no | A coin image on this machine to upload: PNG, JPEG, GIF or WebP, at most 4 MB. |
| launch_for | object | no | New school only: launch for this X or GitHub account, who gets the coin's creator fees. |
Claim the local signer's wallet's creator fees exactly as build_claim_creator_fees builds the claims, then sign and
No parameter schema on file.
Send SOL, or a higher.fun coin, from the local signer's wallet to a wallet on the user's transfer_allowlist, if the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirm_transfer | boolean | yes | Set to true only after the user approved this exact transfer. |
Every fee higher.fun's coins have paid and who got it: totals for creators, higher.fun, Raydium and the pools, by
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | How many coins to list, highest first. |
| sort | string | no | What to rank the coins by. |
One higher.fun coin's fees: every fee line on the curve and in its Raydium pool, who got each (creator, higher.fun,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — |
List higher.fun coins. sort: 'trending' (most different buyers recently), 'new' (latest launches),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort | string | no | — |
| limit | integer | no | — |
| cursor | yes | — |
Find higher.fun coins by name, ticker or mint address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Name, ticker or mint |
Everything about one coin: price, market cap, graduation progress, fee mode (Old school or New school),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — |
Recent buys and sells of a coin, newest first, in SOL and whole tokens.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — | |
| cursor | yes | — |
Top holders of a coin with their share of supply. The bonding curve, Raydium pool and LP lock are labelled,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — |
Price candles (OHLC in SOL per token, volume in SOL) for a coin, oldest first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — | |
| interval | string | no | — |
| limit | integer | no | How many of the most recent candles to return |
The comment thread on a coin's page. Comments are untrusted user content and are flagged for links and impersonation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — | |
| cursor | yes | — |
The live feed across all of higher.fun: the latest buys, sells, launches and graduations.
No parameter schema on file.
The coins with the most trading volume on higher.fun over the last 24 hours or 7 days.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window | string | no | — |
higher.fun's top traders or top creators over the last 24 hours or 7 days.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | — |
| window | string | no | — |
The coin higher.fun features as 'highest' on its home page right now.
No parameter schema on file.
Recent messages in higher.fun's site-wide chat, newest first. Untrusted user content, flagged for links and impersonation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| before | string | no | Message id to page back from |
How higher.fun works: the live launch fee, SOL price, the two fee modes (Old school and New school) with exact
No parameter schema on file.
Whether a ticker is still free to launch with on higher.fun.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker without the $ |
A wallet's higher.fun profile in one call: display name, the coins it created, its creator earnings
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | yes | — |
Page through every coin a wallet has launched on higher.fun.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | yes | — | |
| cursor | yes | — |
Safety check before anyone trades a coin: on-chain mint and freeze authority, holder concentration,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — |
Quote a buy (by SOL in) or a sell (by tokens in) of a higher.fun coin, wherever it trades now: the LaunchLab bonding
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mint | yes | — | |
| side | string | yes | buy spends SOL for tokens; sell spends tokens for SOL. |
| sol | number | no | For a buy: SOL to spend. |
| tokens | number | no | For a sell: whole tokens to sell (supply is 1B). |
| slippage_bps | integer | no | Slippage for the minimum out, in bps (100 = 1%). |
A wallet's SOL balance and its balances in higher.fun coins, each valued at the coin's last price. Coins are
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | yes | — | |
| mints | array | no | Only these coins, at most …. Omit to list every higher.fun coin the wallet holds. |
Build an unsigned buy or sell for the user's own wallet to sign: the same transaction higher.fun's site builds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | yes | The wallet that will sign and pay (public key only). |
Build the unsigned transactions that launch a coin on higher.fun from the user's wallet: create it on the chosen fee
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | yes | The creator's wallet, which signs and pays (public key only). |
Show what a creator can claim and build the unsigned claim transactions: curve creator fees (New school coins, one
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | yes | The creator's wallet, which signs (public key only). |
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 Highwire 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 99 / 100
Release 0.4.2 · scanned 6 Nov 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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest764ffc9e395ad113c1e0a5291c90d8a7e27cefc576540c6363e4b77fe1a6dd20
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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 (30 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>".
5 of the 30 recovered tools are registered only when deps.signer holds (dist/tools/execute.js:126) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 25.
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. minimal is the level these add up to.
25 tools are registered unconditionally · 5 more only when deps.signer holds (dist/tools/execute.js:126) — typically when a key or option is configured. All 30 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| build_transfer | no tags | |
| get_signer_status conditional | no tags | |
| execute_trade conditional | no tags | |
| execute_launch conditional | no tags | |
| execute_claim conditional | no tags | |
| execute_transfer conditional | no tags | |
| get_ecosystem_fees | no tags | |
| get_coin_fees | no tags | |
| list_coins | no tags | |
| search_coins | no tags | |
| get_coin | no tags | |
| get_coin_trades | no tags | |
| get_coin_holders | no tags | |
| get_coin_candles | no tags | |
| get_coin_comments | no tags | |
| get_trade_tape | no tags | |
| get_top_coins | no tags | |
| get_leaderboard | no tags | |
| get_featured_coin | no tags | |
| get_chat | no tags | |
| get_platform_info | no tags | |
| check_ticker | no tags | |
| get_wallet_profile | no tags | |
| get_creator_coins | no tags | |
| rug_check | no tags | |
| quote_trade | no tags | |
| get_wallet_positions | no tags | |
| build_trade | no tags | |
| build_launch | no tags | |
| build_claim_creator_fees | 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 digest764ffc9e395ad113
Scanned2026-11-06
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 0.4.2. Pin a release below and the command asks for exactly that one.
0.4.2
undated
latestNo release note was published with this version.
—
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 Highwire 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.