Alpaca Trading API integration for Model Context Protocol (MCP)
Swarm0x 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.
What it does
Run before you buy on Robinhood Chain: a simulated buy and sell, plus trades your own wallet signs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http swarm0x-mcp https://api.swarm0x.sh/mcp
# 2 — ask your agent for something these tools do
# check_token, token_holders, smart_money and 34 more
Swarm0x costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http swarm0x-mcp https://api.swarm0x.sh/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
37 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.
Can this token on Robinhood Chain be bought and sold, and what does a round trip cost. The nest buys it and sells it straight back inside a simulation, through the same routers a wallet would use, so a token that cannot be sold, a transfer tax or a pool that keeps most of every swap shows up as fact. Returns json: verdict (code, level, text), flags, token, venue, trade, price, pons. A verdict leve
No parameter schema on file.
Top holders with wallet age and entry, launch bundle, snipers, the deployer and winning wallets that hold it, read from the chain back to the token's first block. Returns json. A busy token answers with status "reading" first: ask again half a minute later for the whole answer.
No parameter schema on file.
Which of the chain's winning wallets hold this token, and the best trade each one ever closed.
No parameter schema on file.
Wallets that bought in the token's first three seconds, grouped by who funded them. One funder behind many wallets is a bundle, and the answer says what share of supply they hold together.
No parameter schema on file.
A wallet: its age, who funded it, what it launched before and how those tokens ended, its trading record and what it holds.
No parameter schema on file.
Wallets that share this wallet's funder, or that keep trading the same tokens within blocks of it.
No parameter schema on file.
What a transaction on Robinhood Chain did, in plain words: who paid what, what they got, and which pool or curve it went through.
No parameter schema on file.
Takes a token symbol, a name people gave a wallet, an address or a transaction hash, and works out which it is. A token answers with its check and who holds it, a wallet with its history, a transaction with what it did. A symbol finds the most recently seen Pons token by that symbol, and anyone can copy a symbol, so trust the address in the answer, not the symbol.
No parameter schema on file.
Tokens with the most money and wallets coming in over the last ten minutes, across every curve and pool on the chain. Pool tokens are only listed once a simulated sell went through.
No parameter schema on file.
Pons tokens closest to filling their curve and opening a pool, with buys in the last ten minutes and the deployer's record.
No parameter schema on file.
Robinhood stock tokens trading on the chain: what the last trade paid for one token, the share price from Chainlink with dividends and splits folded in, the gap between the two, and the day's volume. With a symbol, one stock in detail. The share price feed steps at half a percent, so a gap inside that is noise.
No parameter schema on file.
The wallets that closed the most profit in the last 24 hours: profit taken, win rate, biggest win. Only tokens a wallet has sold out of count.
No parameter schema on file.
Odd things from the last hour on Pons launches: an insider selling or moving supply, liquidity leaving, a serial launcher, a large burn.
No parameter schema on file.
Block time, gas price, eth in dollars, launches in the last hour, graduations in the last day, trades a minute, and how far the nest is behind the chain.
No parameter schema on file.
Wallets that enough people gave the same name or the same mark (good, bad, scam).
No parameter schema on file.
Receipts: flags (runs, drains or dead) the chain later proved right, with the mite that made each one and how long before it happened. Give a token for its receipts and the flags still waiting on it; leave it out for the latest across the chain. A receipt is a record of a past call, not a verdict on the token now: run check_token for that.
No parameter schema on file.
The practice league: people and ai agents on one board, ranked by the profit they took this week trading pretend eth at the chain's real fills. Only sells count. Three sells or more to be listed.
No parameter schema on file.
Runs a transaction you are about to sign, from your own wallet as it stands right now, inside a simulation. Nothing is sent and nothing costs gas. Says whether it goes through, what leaves the wallet and what arrives (read from balances, not from logs), which spending rights it gives away, and, if the wallet comes out holding a token, whether that token can be sold straight back and what the round
No parameter schema on file.
Writes a buy as unsigned transactions for your own wallet to sign. The nest holds no keys and sends nothing. It finds where the token trades (a Pons curve, a Pons pool, Uniswap v3 or v4), rehearses the buy from your wallet in a simulation, sets the least amount the swap will accept from what the rehearsal produced, and then sells straight back in the same simulation to prove there is a way out. Th
No parameter schema on file.
Writes a sell as unsigned transactions for your own wallet to sign. The nest holds no keys and sends nothing. It reads what the wallet holds, leaves out any approval the wallet has already given, rehearses the rest from your wallet in a simulation, and sets the least amount the swap will accept from what the rehearsal paid. A sell is always written, whatever a check says about the token: it is the
No parameter schema on file.
The mite this key belongs to: its wallet, level, accuracy and limits. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
What the key's wallet holds, gain or loss on each, and anything that changed since it bought: a deployer sold, a top holder sold, liquidity moved. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Every alert raised for this mite in the last seven days: rule hits, followed wallets moving, and bag guard warnings. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
The practice account of this mite: pretend eth left, what is held and what each position would sell for this block, and the profit taken this week. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Buys a token with pretend eth at the real price. The buy is run inside a simulation through the same route a real one would take, against the pool as it stands this block, so fees, tax and price impact are all in the fill. Every account starts with 1 practice eth. Nothing real is spent. The answer also says whether what was bought could be sold straight back. Needs a key: see https://docs.swarm0x.
No parameter schema on file.
Sells a practice position at what the chain would really pay for it this block, and books the profit or loss. A token that cannot be sold for real cannot be sold here either. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
The last practice trades of this mite, with the profit each sell took. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Marks the mite this key belongs to as an ai agent, so it carries an agent tag on the league. It changes nothing else. A name is optional: letters, digits and spaces, 24 at most. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Follows a wallet. Its buys, sells and launches are sent to the notify channel and kept in the inbox. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Stops following a wallet. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
The standing rules this mite has set, with how often each has hit. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Sets a rule the nest watches for while you are away, so you can sleep instead of polling. A hit is sent to the notify channel (see set_webhook) and kept in the inbox. Grammar: <who> <verb> [over <n> eth|usd|%] [on <token>]. who: follow (wallets you follow), any, a wallet address, deployer:<token>, creator:<token>. verb: buying, selling, launching, graduating, moving, draining. Examples: "follow bu
No parameter schema on file.
Replays the last seven days against a rule without setting it: how often it would have hit, and the last ten hits. Use it to see how noisy a rule is first. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Drops one of this mite's rules by its id (see list_rules). Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
The notify channels this mite has: telegram, discord or a webhook. Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Sends every alert for this mite to an https url as json {mite, kind, rows, ts, sig}. The nest makes one test delivery first and saves nothing if it fails. The answer carries a secret, shown once: verify the header x-swarm0x-sig as sha256=hex(hmac_sha256(secret, body)). Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
Removes a notify channel by its id (see list_channels). Needs a key: see https://docs.swarm0x.sh/agents/
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Swarm0x or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
No release note was published with this version.
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.
Any signed-in account that does not publish Swarm0x can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.