Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.getplexa/mcp

NPM · @GETPLEXA/MCP · SCANNED AUG 3

Economic-safety tools for trading agents: executable quote + rug/honeypot pretrade check via x402.

Available components

+15 this week 21 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security39
  • Malware scan not yet available for this package.Unverified
  • Only part of the dependency tree could be resolved (113 of 117), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (113 of 117), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @getplexa/mcp

# add to Claude Code
claude mcp add com-getplexa-mcp -- npx -y @getplexa/mcp
# add to Codex CLI
codex mcp add com-getplexa-mcp -- npx -y @getplexa/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getplexa-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@getplexa/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-getplexa-mcp --command npx --arg -y --arg @getplexa/mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-getplexa-mcp:
    command: "npx"
    args: ["-y", "@getplexa/mcp"]
// mcp.json
{
  "mcpServers": {
    "com-getplexa-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@getplexa/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 −43
    • Malware scan: pass → unverified security
    • Stability: 0.23 → unverified security
    • Tool coverage: 100 → unverified functional
    • Capabilities: pass → unverified functional
    • Package version: 0.1.5 → 0.1.6 functional
  • 2 Aug 26 +59
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Schema quality: 410 → 508 functional
    • Schema quality: unverified → good functional
    • Stability: unverified → 0.23 functional
    • MCP protocol: unverified → pass functional
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
    • Package version: 0.1.4 → 0.1.5 functional
  • 1 Aug 26 −20
    • Stability: 0.17 → unverified security
    • Tool coverage: 100 → unverified functional
    • Capabilities: pass → unverified functional
    • Package version: 0.1.4 → 0.1.5 functional
  • 31 Jul 26 +19
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Tool coverage: 100 → unverified functional
    • Package version: 0.1.3 → 0.1.4 functional
  • 28 Jul 26 +18
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: unverified functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 6

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@getplexa/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 113 packages

113 packages in the resolved dependency tree · 97 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 2 exposed · ~1,111 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
plexa_pretrade_check ~662

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`. Plus an executable quote sub-result. 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). Heuristic economic signal, NOT financial advice; absence of a proven trap is not…

NameTypeReqDescription
chainstringOptional. The endpoint accepts base | polygon | arbitrum | matic | arbitrum-one | arb | eip155:8453 | eip155:137 | eip155:42161, but the safety flags are Base-tuned, so anything other than base curre…
sizeUSDstringOptional USD notional for the executable-quote sub-result, e.g. "1000" (default 1000). A STRING, not a number; positive, no thousands separator ("1,000" is rejected).
tokenstringyesToken to vet before buying. ERC-20 contract address (0x + 40 hex) on the chain this server is configured for. Not a symbol.

No output schema declared.

No examples provided.

plexa_quote ~449

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. Cost: $0.02 USDC per call via x402 (paid automatically by the configured wallet). Returns informational market data, NOT financial advice.

NameTypeReqDescription
chainstringOptional chain override for THIS quote. Accepted: base | polygon | arbitrum | matic | arbitrum-one | arb | eip155:8453 | eip155:137 | eip155:42161 (case is normalized for you). Omit to use the server…
sizeInstringTrade size as a human amount of tokenIn, e.g. "1.5" for 1.5 WETH. A STRING, not a number. Provide at least one of sizeIn or sizeUSD; if you send both, sizeUSD wins and sizeIn is ignored.
sizeUSDstringTrade size as a USD notional, e.g. "5000". A STRING, not a number; positive, no thousands separator ("5,000" is rejected) and no exponent. Provide at least one of sizeIn or sizeUSD; if you send both,…
tokenInstringyesToken being sold. ERC-20 contract address (0x + 40 hex) on the chain this server is configured for. Not a symbol.
tokenOutstringyesToken being bought. ERC-20 contract address (0x + 40 hex) on the chain this server is configured for. Not a symbol.

No output schema declared.

No examples provided.