Dexploit MCP Server
@dexploit/mcp
npm
v0.2.0
Published by @dexploit — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Model Context Protocol server for Dexploit — Solana DEX swaps, OHLCV, token intel, and pump.fun lifecycle. Lets Claude Code (and other MCP clients) query live Dexploit data while you code.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 51
Each tool and what it can reach — statically extracted from the published source.
get_token_stats_batchingests untrusted inputreads sensitive dataget_positions_batchingests untrusted inputget_tokenreads sensitive dataget_token_auditreads sensitive dataget_token_first_buyersreads sensitive dataget_token_intelreads sensitive dataget_token_positions_batchreads sensitive dataget_token_rugsreads sensitive dataget_token_statsreads sensitive dataget_token_swapsreads sensitive data
Show 41 more tools ↓
get_token_tradersreads sensitive dataget_token_wallet_tag_countsreads sensitive dataget_wallets_batchingests untrusted inputlist_tokensreads sensitive datafind_poolno sensitive capabilityget_candlesno sensitive capabilityget_global_statsno sensitive capabilityget_index_statsno sensitive capabilityget_kol_calendarno sensitive capabilityget_kol_dateno sensitive capabilityget_kol_leaderboardno sensitive capabilityget_kol_leaderboard_periodno sensitive capabilityget_latest_candlesno sensitive capabilityget_pnl_leaderboardno sensitive capabilityget_searchno sensitive capabilityget_swapno sensitive capabilityget_top_moversno sensitive capabilityget_trader_statsno sensitive capabilityget_trader_swapsno sensitive capabilityget_trendingno sensitive capabilityget_wallet_highlightsno sensitive capabilityget_wallet_performanceno sensitive capabilityget_wallet_pnlno sensitive capabilityget_wallet_pnl_chartno sensitive capabilityget_wallet_pnl_historyno sensitive capabilityget_wallet_position_tokenno sensitive capabilityget_wallet_positionsno sensitive capabilityget_wallet_positions_batchno sensitive capabilityget_wallet_riskno sensitive capabilityget_wallet_tagsno sensitive capabilityget_whale_swapsno sensitive capabilitylist_bot_tradersno sensitive capabilitylist_exchange_tradersno sensitive capabilitylist_pairsno sensitive capabilitylist_pool_eventsno sensitive capabilitylist_protocolsno sensitive capabilitylist_pump_lifecycleno sensitive capabilitylist_rugsno sensitive capabilitylist_swapsno sensitive capabilitylist_swaps_rangeno sensitive capabilityrun_screenerno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (51 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>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.0 latest |
A 96/100 | 0 | 1.13.0 | 2026-09-08 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @dexploit/mcp --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.