Loading...
This MCP server manages cryptocurrency portfolios by adding holdings, fetching prices, and visualizing portfolio value history using Binance data.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server manages cryptocurrency portfolios by adding holdings, fetching prices, and visualizing portfolio value history using Binance data.
This server is relatively safe for read operations and basic portfolio management. However, the ability to write to a local database and the lack of authentication mechanisms introduce moderate risks. It's crucial to ensure the server is not exposed to unauthorized access.
Performance is likely limited by the SQLite database and the Binance API. Optimize queries and consider caching price data for improved responsiveness.
Cost is primarily related to Binance API usage. Monitor API usage to avoid exceeding rate limits and incurring unexpected fees.
pip install mcp[cli]{
"mcpServers": {
"crypto-portfolio-mcp": {
"command": "python",
"args": [ "path/to/crypto-portfolio-mcp/main.py" ]
}
}
}USDTget_portfolio_summaryRetrieves a summary of the current cryptocurrency portfolio holdings and their values.
Read-only operation; retrieves existing data.
add_holdingAdds a new cryptocurrency holding to the portfolio with a specified amount.
Writes data to the local database, modifying the portfolio.
get_priceFetches the current price of a given cryptocurrency trading pair from Binance.
Read-only operation; retrieves external data.
portfolio_value_historyGenerates a chart of the portfolio's value over time and displays it as a PNG image.
Read-only operation; generates a visual representation of existing data.
None
cloud
This server is relatively safe for read operations and basic portfolio management. However, the ability to write to a local database and the lack of authentication mechanisms introduce moderate risks. It's crucial to ensure the server is not exposed to unauthorized access.
Autonomy should be carefully considered due to the lack of authentication and the ability to modify the portfolio. Implement safeguards to prevent unintended actions.
Production Tip
Implement input validation and sanitization to prevent SQL injection and other vulnerabilities.
Implement authentication and authorization mechanisms to restrict access. Consider using a firewall to limit network exposure.
The current implementation supports a single portfolio. You would need to modify the code to support multiple portfolios.
Regularly back up the `portfolio.db` file to prevent data loss.
The server will be unable to fetch prices, and portfolio values will not be updated. Implement error handling to gracefully handle API outages.
The current implementation is specific to Binance. You would need to modify the code to support other exchanges using the `ccxt` library.
Optimize database queries, cache price data, and consider using a more robust database system for larger portfolios.
Storing API keys directly in the code is highly discouraged. Use environment variables or a secure configuration file to store sensitive information.