Alpaca Trading API integration for Model Context Protocol (MCP)
Check if a crypto token is a scam before buying. text can be a contract address, a DexScreener or pump.fun link, or a whole forwarded "gem" message, on any of 64 networks (chain "auto" detects it; or pass a DexScreener chain id like "ton", "sui", "tron", "hyperevm"). Returns a rule-based verdict (LOW_RISK, CAUTION, HIGH_RISK, UNKNOWN), a 0-100 risk score, plain-language findings (lan
A call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
What it does
Is this crypto token a scam? Rule-based checks on 64 networks, read-only, no wallet or API key.
Quickstart
# 1 — sign in once: npx mcprush@latest login
# it asks for a key from mcprush.com/dashboard#access
# 2 — install
npx mcprush@latest add darkjay123/rugradar-mcp
# 3 — the plan is chosen at checkout, in the browser
# 4 — ask your agent for something these tools do
# check_token, scan_message, token_history and 2 more
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
You are on the Free tier: 100 calls a month, and call 101 returns a normal MCP error rather than an invoice.
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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add darkjay123/rugradar-mcp write the entry with the key for you; --scope user makes it available in every project.
claude mcp add --transport http --scope user rugradar-mcp https://mcprush.com/gw/rugradar-mcp/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
5 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.
Check if a crypto token is a scam before buying. text can be a contract address, a DexScreener or pump.fun link, or a whole forwarded "gem" message, on any of 64 networks (chain "auto" detects it; or pass a DexScreener chain id like "ton", "sui", "tron", "hyperevm"). Returns a rule-based verdict (LOW_RISK, CAUTION, HIGH_RISK, UNKNOWN), a 0-100 risk score, plain-language findings (lan
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| chain | string | no | — |
| lang | string | no | — |
| amount_ngn | integer | no | — |
| currency | string | no | — |
Scan a crypto pitch message for scam tactics (seed phrase requests, wallet-drainer links, guaranteed returns, urgency, send-to-receive) without touching the network. Private data is stripped.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| lang | string | no | — |
What RugRadar saw the last time this token was checked (verdict, score, pool size, how long ago).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | — |
| address | string | yes | — |
Plain-language meaning of a RugRadar finding code such as HONEYPOT or LP_UNLOCKED.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | — |
| lang | string | no | — |
Fetch a saved RugRadar check by its id (the code at the end of a rugradar-dun.vercel.app/r/... link). Saved checks last 30 days. Re-run check_token before relying on an old one: tokens change fast.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trace_id | string | yes | — |
- 100 calls a month, included
- 5 calls a minute at peak
- Every tool the listing has
- No card needed — call 101 returns a limit error rather than a bill
- Upgrade at any point, prorated to the day
- 1,000 calls a month, included
- 15 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
- 20,000 calls a month, included
- 60 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against the 100 calls a month on Free
| Tool | Unit | Calls used | Out of the monthly allowance |
|---|---|---|---|
| check_token | call | 1 | 1.0000% |
| scan_message | call | 1 | 1.0000% |
| token_history | call | 1 | 1.0000% |
| explain_finding | call | 1 | 1.0000% |
| get_report | call | 1 | 1.0000% |
Failed calls, timeouts and anything the gateway rejects never count. When the allowance runs out the gateway returns an error naming the plan limit — nothing is billed beyond the subscription, ever.
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 a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 1.0.0.
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 RugRadar 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.