onestop
NPM · @ONESTOP-TRADE/ONESTOP-MCP
Gasless Solana swaps, market-cap limit, trailing and TWAP orders, and plans. Your key stays local.
Available components
Last scanned (3 hours ago)
Scores higher than 31% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 144 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3277 tokens (~172/item across 19 items; 19 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 45
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@onestop-trade/onestop-mcp@1.0.2
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 144 packages
| Packages resolved | 144 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
activity ~60
What this MCP did since it started, newest first: fills it signed (with signatures) or refused (with the reason), paper fills, exits it took on, and order and plan updates.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | how many entries, default 20 |
No output schema declared.
No examples provided.
cancel_order ~55
Cancel an order. A slice that's already signed can't be called back; the rest of the order stops. A plan's orders are cancelled with cancel_plan.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | the order_id the order was placed with |
No output schema declared.
No examples provided.
cancel_plan ~42
Cancel a plan and every stage that hasn't run. Tokens already bought stay in the wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | the plan_id the plan was placed with |
No output schema declared.
No examples provided.
connect ~63
Wait up to 20 seconds for the engine login, then report the same as wallet. The MCP logs in by itself at start and again after any drop, backing off up to 30 seconds between tries, so use this to wait for it rather than retrying another tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
extend_order ~52
Set an open order's expiry to expires_h hours from now.
| Name | Type | Req | Description |
|---|---|---|---|
| expires_h | integer | yes | hours from now until it lapses |
| order_id | string | yes | the order_id the order was placed with |
No output schema declared.
No examples provided.
get_order ~49
One order: its status, trigger levels, the market cap it saw last, its slices and its fills with their signatures.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | the order_id the order was placed with |
No output schema declared.
No examples provided.
get_plan ~73
A plan's progress: the entry's fills, the tokens it bought and its average entry market cap, the exit (armed with its high and stop, or its take-profit level), and the market cap now as a multiple of the entry.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | the plan_id the plan was placed with |
No output schema declared.
No examples provided.
holdings ~39
A wallet's SOL and token balances, valued in USD. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | – | the wallet to look at, default this MCP's |
No output schema declared.
No examples provided.
limit_order ~442
A limit order: buy or sell when the market cap crosses a level, given as target_bps of the market cap now (above it, a take profit or a breakout buy; below it, a stop loss or a dip buy) or as target_mcap_usd. It fires only on a cross after placement. Add twap_slices and twap_interval_s to fill in slices. A buy takes amount in lamports; a sell takes amount in raw token units or holdings_bps of the balance when it fires. paper: true rehearses with real prices and never trades. It lapses after expires_h hours if it hasn't fired. Returns the order with its order_id; follow it with get_order. Signing: fills are signed by this MCP process. If it isn't running when an order fires, the fill is queued and executed on reconnect at the then-current price.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | a buy: the SOL to spend, in lamports (1 SOL = 1000000000). A sell: raw token units. Give this or holdings_bps |
| expires_h | integer | – | hours until it lapses if it hasn't fired, default 24 |
| holdings_bps | integer | – | a sell: the share of the wallet's balance when it fires, 10000 = all |
| mint | string | yes | the token's mint address |
| paper | boolean | – | true: rehearse with real prices; fills are recorded, never signed or traded |
| side | string | yes | buy spends SOL on the token; sell sells the token for SOL |
| slippage_bps | integer | – | the most the price may move against a fill, default 300 = 3% |
| target_bps | integer | – | the level as a share of the market cap now: 20000 = 2x, 5000 = half |
| target_mcap_usd | number | – | or the level as a market cap in USD |
| twap_interval_s | integer | – | seconds between slices |
| twap_slices | integer | – | fill in this many slices instead of one swap |
No output schema declared.
No examples provided.
limit_trailing_order ~480
A limit, then a trail: it waits for the market cap to reach the level (target_bps of the market cap now, or target_mcap_usd), then trails from there and fires when the market cap moves back trail_bps from its best. A sell above the market cap now lets a winner run past the target and keeps the gain. Add twap_slices and twap_interval_s to fill in slices. A buy takes amount in lamports; a sell takes amount in raw token units or holdings_bps of the balance when it fires. paper: true rehearses with real prices and never trades. It lapses after expires_h hours if it hasn't fired. Returns the order with its order_id; follow it with get_order. Signing: fills are signed by this MCP process. If it isn't running when an order fires, the fill is queued and executed on reconnect at the then-current price.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | a buy: the SOL to spend, in lamports (1 SOL = 1000000000). A sell: raw token units. Give this or holdings_bps |
| expires_h | integer | – | hours until it lapses if it hasn't fired, default 24 |
| holdings_bps | integer | – | a sell: the share of the wallet's balance when it fires, 10000 = all |
| mint | string | yes | the token's mint address |
| paper | boolean | – | true: rehearse with real prices; fills are recorded, never signed or traded |
| side | string | yes | buy spends SOL on the token; sell sells the token for SOL |
| slippage_bps | integer | – | the most the price may move against a fill, default 300 = 3% |
| target_bps | integer | – | the level as a share of the market cap now: 20000 = 2x, 5000 = half |
| target_mcap_usd | number | – | or the level as a market cap in USD |
| trail_bps | integer | yes | how far the market cap must move back from its best to fire: 1000 = 10% |
| twap_interval_s | integer | – | seconds between slices |
| twap_slices | integer | – | fill in this many slices instead of one swap |
No output schema declared.
No examples provided.
list_orders ~40
This wallet's orders, newest first. An order is waiting, armed (trailing from its best), filling, then filled, cancelled, expired or failed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
place_plan ~375
A plan: an entry buy, then an exit onestop creates for exactly the tokens the entry bought. protect arms once the market cap reaches arm_bps of the entry's (30000 = 3x) and then sells when it falls trail_bps from its high. exit takes profit at target_bps of the entry market cap, or shapes the protected sell (twap, and sell_bps of the tokens); with neither level the exit sells at once. A plan needs protect or exit. To protect tokens already held, leave out entry and give amount or holdings_bps. Returns the plan with its plan_id; follow it with get_plan. Signing: fills are signed by this MCP process. If it isn't running when an order fires, the fill is queued and executed on reconnect at the then-current price.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | without an entry: raw units of the token already held |
| entry | object | – | the buy; leave it out to protect tokens already held |
| exit | object | – | a take profit at target_bps of the entry market cap, and how the exit sells: twap, sell_bps of the tokens (default all) |
| expires_h | integer | – | hours until it lapses if it hasn't fired, default 24 |
| holdings_bps | integer | – | without an entry: or a share of the wallet's balance of it |
| mint | string | yes | the token's mint address |
| paper | boolean | – | true: rehearse with real prices; fills are recorded, never signed or traded |
| protect | object | – | a trailing stop that arms at arm_bps of the entry market cap |
| slippage_bps | integer | – | the most the price may move against a fill, default 300 = 3% |
No output schema declared.
No examples provided.
quote ~201
Price a swap without trading. Returns amount_in, expected_out, min_out, the fee and the gas (both taken from the trade), and transaction.base64: the unsigned transaction, good for about 45 seconds. Nothing is signed or sent. Pass the transaction to submit_swap to trade it after looking at the quote, or use swap to do both at once.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | raw units of the input (lamports for SOL). Give this or holdings_bps |
| holdings_bps | integer | – | or a share of the wallet's balance of the input, 10000 = all |
| input | string | yes | what to spend: a mint, or SOL, USDC, USDT |
| output | string | yes | what to get: a mint, or SOL, USDC, USDT |
| slippage_bps | integer | – | the most the price may move against a fill, default 300 = 3% |
No output schema declared.
No examples provided.
submit_swap ~166
Trade a transaction from quote. The MCP checks it with the guard first, simulating it on the wallet's own RPC: onestop pays the fee, only this wallet signs besides it, nothing approves or reassigns the wallet's accounts, the wallet loses no more than the quote says, and the output arrives. Then it signs, sends it through onestop's MEV-protected lane and waits for it to land. Only a transaction this MCP quoted recently is accepted, because the guard needs its quote and onestop co-signs only trades it quoted. Returns confirmed with the signature and the wallet's balance changes, or refused with the guard's reasons. With dry run it stops after the guard.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction | string | yes | transaction.base64 from a quote |
No output schema declared.
No examples provided.
swap ~199
Swap now in one call: quote, guard, sign and send, the same as quote followed by submit_swap. No SOL needed for gas: onestop pays it and takes it, with any fee, from the trade. Returns the amounts and the result: confirmed with the signature and balance changes, refused with the guard's reasons, or dry_run.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | raw units of the input (lamports for SOL). Give this or holdings_bps |
| holdings_bps | integer | – | or a share of the wallet's balance of the input, 10000 = all |
| input | string | yes | what to spend: a mint, or SOL, USDC, USDT |
| output | string | yes | what to get: a mint, or SOL, USDC, USDT |
| slippage_bps | integer | – | the most the price may move against a fill, default 300 = 3% |
No output schema declared.
No examples provided.
tokens ~37
Price, market cap, liquidity and main pool for up to 100 tokens. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| mints | array | yes | token mint addresses |
No output schema declared.
No examples provided.
trailing_order ~393
A trailing order: a sell follows the market cap up and fires when it falls trail_bps from its high; a buy follows it down and fires when it rises trail_bps from its low. Add twap_slices and twap_interval_s to fill in slices. A buy takes amount in lamports; a sell takes amount in raw token units or holdings_bps of the balance when it fires. paper: true rehearses with real prices and never trades. It lapses after expires_h hours if it hasn't fired. Returns the order with its order_id; follow it with get_order. Signing: fills are signed by this MCP process. If it isn't running when an order fires, the fill is queued and executed on reconnect at the then-current price.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | a buy: the SOL to spend, in lamports (1 SOL = 1000000000). A sell: raw token units. Give this or holdings_bps |
| expires_h | integer | – | hours until it lapses if it hasn't fired, default 24 |
| holdings_bps | integer | – | a sell: the share of the wallet's balance when it fires, 10000 = all |
| mint | string | yes | the token's mint address |
| paper | boolean | – | true: rehearse with real prices; fills are recorded, never signed or traded |
| side | string | yes | buy spends SOL on the token; sell sells the token for SOL |
| slippage_bps | integer | – | the most the price may move against a fill, default 300 = 3% |
| trail_bps | integer | yes | how far the market cap must move back from its best to fire: 1000 = 10% |
| twap_interval_s | integer | – | seconds between slices |
| twap_slices | integer | – | fill in this many slices instead of one swap |
No output schema declared.
No examples provided.
twap_order ~349
A TWAP order: buy or sell now in twap_slices swaps twap_interval_s seconds apart, to spread the price impact. Each slice is what's left divided by the slices left. A buy takes amount in lamports; a sell takes amount in raw token units or holdings_bps of the balance when it fires. paper: true rehearses with real prices and never trades. It lapses after expires_h hours if it hasn't fired. Returns the order with its order_id; follow it with get_order. Signing: fills are signed by this MCP process. If it isn't running when an order fires, the fill is queued and executed on reconnect at the then-current price.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | a buy: the SOL to spend, in lamports (1 SOL = 1000000000). A sell: raw token units. Give this or holdings_bps |
| expires_h | integer | – | hours until it lapses if it hasn't fired, default 24 |
| holdings_bps | integer | – | a sell: the share of the wallet's balance when it fires, 10000 = all |
| mint | string | yes | the token's mint address |
| paper | boolean | – | true: rehearse with real prices; fills are recorded, never signed or traded |
| side | string | yes | buy spends SOL on the token; sell sells the token for SOL |
| slippage_bps | integer | – | the most the price may move against a fill, default 300 = 3% |
| twap_interval_s | integer | yes | seconds between slices |
| twap_slices | integer | yes | fill in this many slices instead of one swap |
No output schema declared.
No examples provided.
wallet ~64
This MCP's wallet address and its link to onestop: whether it's logged in to the engine, the API it uses, whether dry run is on, and how many orders and plans it's tracking. No network call. Call it first: every other tool acts for this wallet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the onestop MCP server?
onestop runs locally as an npm package, launched with npx -y @onestop-trade/onestop-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 · @onestop-trade/onestop-mcp
claude mcp add trade-onestop-onestop-mcp -- npx -y @onestop-trade/onestop-mcp
What is the onestop MCP server?
onestop is an MCP server listed in the public MCP registry as trade.onestop/onestop-mcp. Gasless Solana swaps, market-cap limit, trailing and TWAP orders, and plans. Your key stays local. This page covers its npm package (@onestop-trade/onestop-mcp).
Is the onestop MCP server safe to use?
onestop scores 60 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 onestop MCP server expose?
onestop exposes 19 tools: wallet, connect, quote, submit_swap, swap, and 14 more. Their descriptions and schemas cost roughly 3,179 tokens of context every time the server is loaded.
Is the onestop MCP server still maintained?
onestop is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.