This project has been quarantined by PyPI admins. It cannot be installed or modified until a security review is complete.
AEVO MCP Server
MCP server for trading on AEVO — works with Claude Code, Claude Desktop, or any MCP client.
Quick Start (Docker + Claude Code)
1. Clone and configure
git clone https://github.com/ribbon-finance/aevo-mcp.git
cd aevo-mcp
cp .env.example .env
Edit .env with your AEVO credentials (get them from app.aevo.xyz/settings):
AEVO_API_KEY=your_key
AEVO_API_SECRET=your_secret
AEVO_SIGNING_KEY_PRIVATE_KEY=your_signing_key
2. Start the server
docker compose up --build -d
3. Connect Claude Code
claude mcp add --transport http aevo-trading http://localhost:8080/mcp
4. Test it
Open a new Claude Code session and type:
call the ping tool
You should see {"ok": true, "result": {"status": "ok"}}. Try check my account balance to verify your credentials work.
Alternative Setup
Local (no Docker)
pip install -e .
cp .env.example .env # edit with your credentials
aevo-mcp --transport stdio
Then connect Claude Code via stdio:
claude mcp add --transport stdio aevo-trading -- aevo-mcp --transport stdio
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
With Docker (recommended):
{
"mcpServers": {
"aevo-trading": {
"type": "http",
"url": "http://localhost:8080/mcp"
}
}
}
With local install:
{
"mcpServers": {
"aevo-trading": {
"command": "aevo-mcp",
"args": ["--transport", "stdio"],
"env": {
"AEVO_API_KEY": "your_key",
"AEVO_API_SECRET": "your_secret",
"AEVO_SIGNING_KEY_PRIVATE_KEY": "your_signing_key"
}
}
}
}
Environment Variables
| Variable | Required | Description |
|---|---|---|
AEVO_API_KEY |
Yes* | API key |
AEVO_API_SECRET |
Yes* | API secret |
AEVO_SIGNING_KEY_PRIVATE_KEY |
Yes | Signing key for order submission |
AEVO_ENVIRONMENT |
No | testnet or mainnet (default) |
AEVO_WALLET_ADDRESS |
No | Wallet address (for register_account tool) |
AEVO_WALLET_PRIVATE_KEY |
No | Wallet private key (for register_account tool) |
AEVO_AUTO_REGISTER |
No | Auto-register on startup (true/false) |
* Don't have API keys? Set AEVO_WALLET_ADDRESS + AEVO_WALLET_PRIVATE_KEY and use the register_account tool to generate them. Advise to have a account and use aevo wallet to generate keys.
What's Included
Tools: markets, account, portfolio, positions, orderbook, build_order, create_order, cancel_order, cancel_all, register_account, and more.
Prompts: trade_plan, risk_checklist, cancel_plan, onboarding_plan
Resources: aevo://status, aevo://markets/summary, aevo://account/overview
Tests
pip install -e ".[test]"
pytest -q tests/
Metadata
Release files for mcp-aevo-server 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_aevo_server-0.2.0.tar.gz | 40.0 kB | Without provenance | Details for mcp_aevo_server-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_aevo_server-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_aevo_server-0.2.0-py3-none-any.whl |
Total release size: 76.6 kB
Release files / mcp_aevo_server-0.2.0.tar.gz
| Download URL | mcp_aevo_server-0.2.0.tar.gz |
|---|---|
| Size | 40.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93a7770c7d891030bfc5de5713ae6549d143caa5b67ceaba145dceeab266ae53
|
|
BLAKE2b-256 checksum How to use checksums |
3472d9327b5613e06be45684446c25541c52a35ce6034444efd50e627d1f9c91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / mcp_aevo_server-0.2.0-py3-none-any.whl
| Download URL | mcp_aevo_server-0.2.0-py3-none-any.whl |
|---|---|
| Size | 36.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
15e0b95a110709c82dbbc25f2f2d7b3c5b87f8209c54656e0ca9d777bb2bad75
|
|
BLAKE2b-256 checksum How to use checksums |
2e2c92152d5e72559046cfe2ffadd07572e2457951e302b6ebcb76290121210e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for mcp-aevo-server 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.