
Defi Orchestrator
io.github.lordbasilaiassistant-sudoPublished by GitHub account lordbasilaiassistant-sudov1.0.2Updated Oct 27, 2026
Multi-step DeFi strategy orchestration — swaps, lending, yields on Base/EVM
Overview
Local MCP server that lets an assistant orchestrate multi-step DeFi strategies — swaps, lending and yield actions — on Base and other EVM chains.
- What you can do
- Plan and run multi-step DeFi strategies on Base/EVM chains
- Execute swaps and lending or yield actions on-chain
- Use a configured RPC endpoint, defaulting to Base mainnet
- Unlock execution access with a premium API key
- No tool list is published, so exact operations are not documented.
- When to use it
- Worth considering if you want an assistant to build and carry out DeFi strategies such as swaps, lending or yield moves on Base or another EVM chain, and you are comfortable giving it a funded wallet key.
- Requirements
- Runs as a local stdio process (npm package, desktop only). Needs an RPC_URL (defaults to Base mainnet), a DEPLOYER_PRIVATE_KEY for on-chain execution, and a THRYX_API_KEY for premium execution access. No authentication is declared beyond these secrets.
Installation
In SourceWeft
- Open Defi Orchestrator in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.