Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Dexpaprika 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.
96/100
trust score
243
downloads a day
local
runs on your machine
3k
downloads in 30d
What it does
A Model Context Protocol server for DexPaprika cryptocurrency data with network-specific pool queries
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user dexpaprika-mcp '--' npx -y dexpaprika-mcp
# 2 — ask your agent for something these tools do
# getKeyStatus, getNetworks, getCapabilities and 17 more
Dexpaprika costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 2 servers
coinpaprika2 servers
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 runs on your machine: your client starts Dexpaprika as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
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 dexpaprika-mcp '--' npx -y dexpaprika-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free 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 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
20 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.
Report whether this server is sending an API key and which plan the API sees.
No parameter schema on file.
List every blockchain network DexPaprika indexes, each row carrying its network id (slug), 24h volume, transaction count, and pool count. Read-only and keyless. Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires as its 'network' argument. Use for…
No parameter schema on file.
Get the static agent onboarding guide for this server: supported workflows, network name synonyms (mapping words like 'eth' to the canonical slug 'ethereum'), recommended call sequences, and common pitfalls. Read-only and keyless. Read it once at the start of a session before your first query, or…
No parameter schema on file.
List the DEXes (exchanges) operating on one network, such as Uniswap on ethereum or Raydium on solana, returned under 'dexes' with page_info (page, total_pages). Read-only and keyless. Use for 'which DEXes are on Base?', 'does Solana have Orca?', or to get a dex id to feed into getDexPools. Scope…
No parameter schema on file.
Get the top liquidity pools across a whole network, ranked by 24h volume by default, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. This is the primary chain-wide pool discovery tool. Use for 'biggest pools on ethereum', 'top trading pairs on Base', or 'most…
No parameter schema on file.
Get the pools belonging to one specific DEX on one network, e.g. all Uniswap v3 pools on ethereum. Proxies /networks/{network}/pools/search with a dex_name filter (the old /networks/{network}/dexes/{dex}/pools endpoint was removed): rows come back under 'results' with cursor pagination…
No parameter schema on file.
Get pools on one network filtered by numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getNetworkPools when the user gives numeric constraints or a time window. Use for 'pools over $1M liquidity on Base', 'pools created in the…
No parameter schema on file.
Get the full current snapshot for one pool by address: its two tokens, current price, liquidity/TVL, 24h volume, and transaction counts, returned as a single pool object (not a list). Read-only and keyless. Use after search or getNetworkPools surfaces a pool, or for 'price/TVL of this pool?' or…
No parameter schema on file.
Get historical OHLCV candles (open, high, low, close, volume) for one pool over a time range, returned as a time-series array. Read-only and keyless. Use for 'price history of this pair', 'hourly chart for the last day', or backtesting; for the single current price use getPoolDetails instead.…
No parameter schema on file.
Get one pool's recent individual swap transactions, newest first, returned under 'transactions' (paginate with page, or a cursor). Read-only. Requires a Dev, Pro or Enterprise key since 30 September 2026: set DEXPAPRIKA_API_KEY to it and DEXPAPRIKA_API_BASE_URL to https://api-pro.dexpaprika.com.…
No parameter schema on file.
Get one token's data and metadata by contract address on one network: multi-timeframe price and volume metrics, plus name, website, Twitter, and Telegram links, returned as a single token object. Read-only and keyless. Use for 'price and volume for 0x... on Base' or 'tell me about this token'. If…
No parameter schema on file.
Get the liquidity pools that contain a specific token on one network, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Use for 'which pools hold WETH on ethereum?' or 'liquidity venues for 0x...'. Network-scoped, so run search first if unsure of the network;…
No parameter schema on file.
Get historical USD OHLCV candles for one token over a time range, returned as a time-series array. The price and volume are computed across every pool the token trades in on the network (a volume-weighted price, and volume summed across those pools), not a single pair. Requires a Dev or Pro plan:…
No parameter schema on file.
Get current USD prices for up to 10 tokens on the same network in one batched call, returned as a prices array plus a missing_tokens list. Read-only and keyless. Tokens that cannot be priced come back in missing_tokens rather than being dropped, so check that list for partial failures. Use for…
No parameter schema on file.
Get tokens on one network matching numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getTopTokens when the user gives numeric constraints or a time window. Use for 'tokens with FDV over $10M on Base', 'newly created tokens…
No parameter schema on file.
Get the top tokens on one network ranked by volume, liquidity, transactions, FDV, or 24h price change, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Use for 'top gainers on Solana', 'highest-volume tokens on Base', or 'biggest tokens by FDV on ethereum'. For…
No parameter schema on file.
Search across ALL networks at once for tokens, pools, and DEXes by name, symbol, or address, returning three arrays: 'tokens', 'pools', and 'dexes'. Read-only and keyless. This is the cross-chain entry point when you do not yet know which network something lives on; once you have a network slug…
No parameter schema on file.
Get platform-wide totals for DexPaprika: the number of networks, DEXes, pools, and tokens indexed, returned as a single summary object. Read-only and keyless. Use for 'how much data do you cover?', 'how many chains or pools total?', or a one-line coverage summary. These are ecosystem-wide counts,…
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
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 Dexpaprika 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 96 / 100
Release 2.8.0 · scanned 14 Oct 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 score96
Findings6 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest6434257cc9a434be4b8dd119befb8a2283a424d80797e50dd033e4b68bdda4b8
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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 (20 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>".
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| getKeyStatus | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getNetworks | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getCapabilities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getNetworkDexes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getNetworkPools | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getDexPools | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getNetworkPoolsFilter | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getPoolDetails | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getPoolOHLCV | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getPoolIndicator | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getPoolTransactions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getTokenDetails | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getTokenPools | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getTokenOHLCV | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getTokenIndicator | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getTokenMultiPrices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| filterNetworkTokens | sensitive-sourceuntrusted-input | sensitive-source: keyword "get_token"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getTopTokens | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| getStats | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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 digest6434257cc9a434be
Scanned2026-10-14
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 2.8.0. Pin a release below and the command asks for exactly that one.
2.8.0
13 Oct 2026
latestNo release note was published with this version.
2.7.3
12 Oct 2026
No release note was published with this version.
2.7.2
2 Oct 2026
No release note was published with this version.
2.7.1
29 Sep 2026
No release note was published with this version.
2.5.1
17 Sep 2026
No release note was published with this version.
2.5.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Dexpaprika 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.