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

io.github.lordbasilaiassistant-sudo/defi-orchestrator

NPM · @THRYX/DEFI-ORCHESTRATOR-MCP-SERVER

Multi-step DeFi strategy orchestration — swaps, lending, yields on Base/EVM

0 this week 71 Trust /100

Last scanned (13 hours ago)

Scores higher than 42% of npm servers

Category Crypto and Web3

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 228 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 753 tokens (~150/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "defi_execute_strategy" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 0
    • Stability: pass → 0.97 functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@thryx/defi-orchestrator-mcp-server@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 103 packages
Packages resolved 103
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~753 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
defi_check_positions ~125

Check ALL DeFi positions for a wallet in one call. Returns lending positions (Aave: supplied, borrowed, health factor, liquidation risk), token balances, and an overall portfolio summary with risk assessment. Tells the agent exactly what actions to consider.

NameTypeReqDescription
chainstring–Chain: 'base' (default), 'ethereum', 'arbitrum'
protocolsarray–Filter to specific protocols: ['aave', 'uniswap', 'aerodrome']. Default: all.
walletstringyesWallet address to check (0x...)

No output schema declared.

No examples provided.

defi_execute_strategy ~134

Execute a previously simulated DeFi strategy on-chain. REQUIRES confirm=true as a safety rail. Executes steps sequentially, reporting each transaction. Stops immediately if any step fails. Returns all tx hashes, gas used, and final state.

NameTypeReqDescription
api_keystringyesPremium API key for execution access
confirmbooleanyesMust be true to execute. Safety rail to prevent accidental execution.
slippage_bpsnumber–Max slippage in basis points (100 = 1%). Default: 100
strategy_idstringyesStrategy ID from a previous defi_simulate_strategy call

No output schema declared.

No examples provided.

defi_get_yields ~108

Get best yield opportunities across DeFi protocols on Base. Returns top pools by APY with TVL, risk rating, and direct comparisons. Helps agents recommend where to deploy capital.

NameTypeReqDescription
chainstring–Chain: 'base' (default)
min_tvlnumber–Minimum TVL in USD to include. Default: 10000
tokenstring–Filter by token symbol (e.g. 'ETH', 'USDC'). Omit for all.

No output schema declared.

No examples provided.

defi_quick_swap ~214

Quick single token swap with best execution across DEXes (Uniswap V3, Aerodrome). Compares quotes from multiple routes and executes on the best one. Returns tx hash, amounts, price impact, and gas used.

NameTypeReqDescription
amountstringyesAmount to swap in human-readable form (e.g. '1.5' for 1.5 ETH)
api_keystring–Premium API key for execution
chainstring–Chain: 'base' (default), 'ethereum', 'arbitrum'
confirmboolean–Set true to execute. False returns quote comparison only.
from_tokenstringyesToken to sell: symbol (ETH, USDC, WETH) or contract address
slippage_bpsnumber–Max slippage in basis points (100 = 1%). Default: 100
to_tokenstringyesToken to buy: symbol (ETH, USDC, WETH) or contract address

No output schema declared.

No examples provided.

defi_simulate_strategy ~172

Simulate a multi-step DeFi strategy WITHOUT executing. Takes natural language like 'swap 1 ETH to USDC' or 'provide ETH/USDC liquidity on Aerodrome'. Returns step-by-step plan with gas estimates, risk assessment, and simulated outcome. Use the returned strategy_id with defi_execute_strategy to execute.

NameTypeReqDescription
chainstring–Chain name: 'base' (default), 'ethereum', 'arbitrum'
paramsobject–Optional explicit parameters to override parsed values: tokenIn, tokenOut, amount, tokenA, tokenB, etc.
strategystringyesNatural language strategy description, e.g. 'swap 1 ETH to USDC on Uniswap', 'provide ETH/USDC liquidity', 'supply 2 ETH to Aave'

No output schema declared.

No examples provided.

Install

How do I install the io.github.lordbasilaiassistant-sudo/defi-orchestrator MCP server?

io.github.lordbasilaiassistant-sudo/defi-orchestrator runs locally as an npm package, launched with npx -y @thryx/defi-orchestrator-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @thryx/defi-orchestrator-mcp-server

# add to Claude Code
claude mcp add lordbasilaiassistant-sudo-defi-orchestrator -- npx -y @thryx/defi-orchestrator-mcp-server
Common questions

What is the io.github.lordbasilaiassistant-sudo/defi-orchestrator MCP server?

io.github.lordbasilaiassistant-sudo/defi-orchestrator is an MCP server listed in the public MCP registry as io.github.lordbasilaiassistant-sudo/defi-orchestrator. Multi-step DeFi strategy orchestration, swaps, lending, yields on Base/EVM. This page covers its npm package (@thryx/defi-orchestrator-mcp-server).

Is the io.github.lordbasilaiassistant-sudo/defi-orchestrator MCP server safe to use?

io.github.lordbasilaiassistant-sudo/defi-orchestrator scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.lordbasilaiassistant-sudo/defi-orchestrator MCP server expose?

io.github.lordbasilaiassistant-sudo/defi-orchestrator exposes 5 tools: defi_simulate_strategy, defi_execute_strategy, defi_quick_swap, defi_check_positions, defi_get_yields. Their descriptions and schemas cost roughly 753 tokens of context every time the server is loaded.

Is the io.github.lordbasilaiassistant-sudo/defi-orchestrator MCP server still maintained?

io.github.lordbasilaiassistant-sudo/defi-orchestrator is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.lordbasilaiassistant-sudo/defi-orchestrator MCP server under?

io.github.lordbasilaiassistant-sudo/defi-orchestrator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.lordbasilaiassistant-sudo/defi-orchestrator MCP server?

VerifyMCP ran 15 checks on io.github.lordbasilaiassistant-sudo/defi-orchestrator, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.lordbasilaiassistant-sudo/defi-orchestrator: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.