servers / com-getplexa-mcp
com.getplexa/mcp
communitystdiolocalverifiedhealthy
Economic-safety tools for trading agents: executable quote + rug/honeypot pretrade check via x402.
01Tools · 2
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| plexa_quote Get EXECUTABLE on-chain liquidity for a swap (Base / Polygon / Arbitrum) before trading: the real fill price under a given size (not the mid/spot quote), price impact in bps, realizable depth, the route (per-leg dex/pool/fee), worst-case slippage, and a confidence rating. Sources Uniswap v3 + Aerodrome/Algebra via canonical on-chain quoters. Call this when an agent needs to know what price a swap of a specific size will ACTUALLY execute at, especially for thin/long-tail tokens. `spotPrice` is NULLABLE: when no reference mid is defensible at this size, `spotPrice` and `priceImpactBps` come back null rather than confidently wrong — an impact measured against a moving origin is worse than no impact at all. Every response carries `validUntil` (epoch ms): asking again before it returns the same answer. It is a statement about when WE recompute, not a promise that the market held still. Cost: $0.02 USDC per call via x402 (paid automatically by the configured wallet). Returns informational market data, NOT financial advice. | read | false | unknown |
| plexa_pretrade_check Two-level economic-safety check for a token on Base before buying it. LEVEL 1 — verdict: "avoid" ONLY when a listed trap is PROVEN on-chain at that block (NO_EXIT_VENUE: no pool exists to sell back into; EXIT_LIQUIDITY_DRAINED: the counter-asset pot is smaller than 5% of the size you asked about — the pot is an upper bound on what a sale can return, so under 5% you recover at most 5 cents on the dollar; TRADING_DISABLED: the token's own trading gate reads false). "clear" means none of them fired — it is NOT a safety rating and NOT a prediction, so do not treat it as "safe". LEVEL 2 — risk_profile: token age, holder concentration (ANY token age: top-1/top-10 share of supply computed from holder balances and on-chain totalSupply; the data age travels in the response, and a vendor outage answers "unknown" with an explicit reason, never a clean default), liquidity structure including exitLiquidityUsd (the pot a sell would be paid from), oracle availability, and fee-on-transfer / blacklist / limit fingerprints — reported as measured DATA with plain-language notes, not as severities. Weigh them yourself: on 40 outcome-labelled Base tokens those structural factors marked live and dead tokens at the same rate, which is why they no longer produce a verdict. CONFIDENCE means different things on the two branches: on "avoid" it is confidence in the TRIGGER, which is a measurement taken that call, so it is always "high" — do NOT gate on it (`if confidence < high: ignore` would skip a proven trap); on "clear" it is how complete the checks were, and there it is worth reading. Gaps are always reported explicitly in `reasons` and as nulls in `risk_profile`. FRESHNESS AND COMPLETENESS: `validUntil` (epoch ms) is until when asking again returns THIS answer — a statement about our recomputation, not about the market. `coverage` {axesExpected, axesReporting} is how many of the 5 axes produced a result. EXIT MEASURABILITY: `liquidityCoverage` is a top-level block that says whether the exit check reached a CONCLUSION, so you do not have to infer it from the numbers. `conclusive: true` with `poolsFound: 0` means every covered factory was queried and no pool exists — that is a measurement, and it is what raises NO_EXIT_VENUE; `conclusive: false` means an AMM we cannot measure holds this token, so exit triggers are not raised on this call; `poolsFound: null` with `factoriesChecked: 0` means discovery did not run at all. `factoriesChecked` is 13 liquidity factories (Uniswap v3, Aerodrome AMM + 3 Slipstream, Pancake v3, Sushi v3, 6 v2-family) covering 77.5% of 30-day Base DEX volume; `venuesUnread` counts venues that simply did not answer this call (retrying may complete the answer), `unmeasuredVenues` / `unmeasuredVenueNames` cover both those and AMMs we cannot measure by design. SINGLETON AMMs (Uniswap v4) are simulated per pool through the canonical V4Quoter, so hooks execute, and the three outcomes are separate counts: `singletonPoolsCounted` (simulation succeeded, proceeds are inside exitLiquidityUsd), `singletonPoolsRejected` (the chain refused the sale — a measurement about that pool, not a gap in our data), and pools left unqueried because the scan hit its work cap, flagged by `singletonScanTruncated`. `singletonPoolsSeen` is the total found and `singletonPoolsHooked` how many run a hook inside the swap. `asOfBlockFirst` and `asOfBlock` are the Base blocks at the start and end of the liquidity reads: equal means the axis was read inside one block and is reproducible there, different means no single block describes it and the gap is the size of that uncertainty. HOLDER DATA AGE: `risk_profile.concentration` carries `ageSec` and `stale`. `ageSec: null` with `stale: false` means read on this call; a number means measured that many seconds ago; `stale: true` means the holder source was unreachable and the LAST KNOWN measurement is reported instead of nothing (confidence drops); `stale: null` means there is no holder value at all, so there is nothing for the freshness flag to describe. `holdersExact: false` means the TOTAL number of holders is unknown (a tariff limit on our side) — the top-10 shares themselves are complete. Plus an executable quote sub-result (`spotPrice` is nullable there — see plexa_quote). v2 since 2026-08-01: the old ok / caution / avoid scale is gone. Base-only today (configure the server with CHAIN=base to use it). Cost: $0.05 USDC per call via x402 (paid automatically by the configured wallet). Support: support@getplexa.com · https://t.me/getplexa_bot · https://github.com/plexa-xyz · https://getplexa.com. Heuristic economic signal, NOT financial advice; absence of a proven trap is not a guarantee of safety. | read | false | unknown |
02Install & source
npx -y @getplexa/mcp
npx- repohttps://github.com/plexa-xyz/mcp
- licenseMIT
- adoption0 stars · 0 forks
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-08-21 16:24Z
next_check2026-08-21 19:20Z
cadenceevery 3h
verifiedtools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed
index_statusindex — 8 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README.
[](https://mcpexplorer.com/servers/com-getplexa-mcp)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →