How wshobson/mcp-trader works
Project type and purpose
• From the README we see this is an “MCP server” (likely a middleware/trading proxy component) that has been archived and superseded by a completely new implementation at maverick-mcp.
(empty) file structure
• Top‐level contains only README.md.
• No code directories, no configuration files, no clients or services here.
• Conclusion: We cannot reverse‐engineer an architecture from this archive; instead, we must apply these guidelines to the new codebase.
README for additional insights
• The README points to https://github.com/wshobson/maverick-mcp.
• That new repo will contain the actual implementation, modules, dependencies, and suggested architecture.
Detail without overthinking
• key modules, even if small (e.g. config loader, logger, health‐check).
• data flow end‐to‐end: from client request down to database write and external API call.
1. Clone the new repo: git clone https://github.com/wshobson/maverick-mcp.git
2. Top‐level directories (e.g. src/api, src/core, src/plugins, deploy/)