# @thryx/defi-orchestrator-mcp-server

MCP server for multi-step DeFi strategy orchestration — simulate, execute, and monitor compound DeFi strategies with safety rails

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** Anthony
- **License:** MIT
- **npm:** @thryx/defi-orchestrator-mcp-server
- **Source:** https://github.com/lordbasilaiassistant-sudo/mcp-servers
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 24 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-31T05:28:08.008Z
- **Version scanned:** 1.0.2
- **CVEs:** none found by OSV at scan time

## Tools

5 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `defi_check_positions` — Check ALL DeFi positions for a wallet in one call. Returns lending positions (Aave: supplied, borrowed, health factor, liquidation risk), token balances, and an
- `defi_get_yields` — 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
- `defi_simulate_strategy` — 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 st
- `defi_execute_strategy` — Execute a previously simulated DeFi strategy on-chain. REQUIRES confirm=true as a safety rail. Executes steps sequentially, reporting each transaction. Stops im
- `defi_quick_swap` — 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 

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"defi-orchestrator-mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@thryx/defi-orchestrator-mcp-server\"\n      ],\n      \"env\": {\n        \"THRYX_API_KEY\": \"<YOUR_THRYX_API_KEY>\",\n        \"DEPLOYER_PRIVATE_KEY\": \"<YOUR_DEPLOYER_PRIVATE_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `THRYX_API_KEY` — Thryx API Key (optional)
- `DEPLOYER_PRIVATE_KEY` — Deployer Private Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 2 credentials (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 25, ceiling 25 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40thryx%2Fdefi-orchestrator-mcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40thryx%2Fdefi-orchestrator-mcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40thryx%2Fdefi-orchestrator-mcp-server
- HTML page: https://forgeregistry.com/registry/%40thryx%2Fdefi-orchestrator-mcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.