{"id":"cortex-ai-software-autonomous-ai-trading-agent-mcp-flash-arb-engine","name":"Autonomous-AI-Trading-Agent-MCP-Flash-Arb-Engine","homepage":"https://www.cortex.io","repo_url":"https://github.com/Cortex-AI-Software/Autonomous-AI-Trading-Agent-MCP-Flash-Arb-Engine","category":"ai-ml","subcategories":[],"tags":["ai-agent","mcp-server","model-context-protocol","crypto","trading","arbitrage","flash-arb","mev-bot","solana","evm","automation"],"what_it_does":"A desktop and developer-focused tool that claims to provide an autonomous AI trading agent (via MCP) and a multi-chain flash-arbitrage execution engine across Solana and multiple EVM/L2 networks, including “MEV protection” and “slippage protection.”","use_cases":["Detect cross-chain / cross-DEX price discrepancies and attempt automated arbitrage execution","Use an MCP-integrated agent for “on-chain context” reasoning for trading decisions","Run a local/desktop workflow to experiment with automated trading strategies"],"not_for":["Automated trading without adequate security review, key management, and risk controls","Production high-frequency trading without verifying execution correctness, counterparty/liquidity assumptions, and operational safety","Users who require clear compliance, audit logs, and formal reliability/SLA documentation"],"best_when":"You need a developer-friendly prototype to experiment with MCP-driven agent workflows and automated arbitrage logic, and you can independently validate safety and performance.","avoid_when":"You need a well-specified, audited, production-grade trading system with clear API contracts, documented rate limits, and robust operational/error semantics.","alternatives":["Generic MCP-compatible agent frameworks (where you supply your own trading execution layer)","Open-source arbitrage/DEX routing bots with explicit contract-based execution and thorough testing","Managed trading/execution infrastructure from reputable providers (when available)"],"af_score":29.0,"security_score":28.2,"reliability_score":16.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:31:14.686264+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":["Python","Node.js"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Wallet connection (implied via on-screen setup)","API keys for CEX/DEX (mentioned as prerequisites)"],"oauth":false,"scopes":false,"notes":"No concrete auth method details, key handling approach, or scope model are documented in the provided README excerpt. Authentication/authorization appears to rely on wallet connection and externally supplied CEX/DEX API keys."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing details beyond a low-entry testing claim ($10 USDT) are provided in the excerpt."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":29.0,"security_score":28.2,"reliability_score":16.2,"mcp_server_quality":35.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":5.0,"tls_enforcement":30.0,"auth_strength":35.0,"scope_granularity":20.0,"dependency_hygiene":30.0,"secret_handling":25.0,"security_notes":"The excerpt mentions wallet connectivity and the use of CEX/DEX API keys but provides no specifics on TLS enforcement, secret storage/handling, scope granularity, key rotation, audit logging, or secure transaction signing. A “MEV protection” claim is present, but no technical implementation details are provided to verify security properties.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":20.0,"error_recovery":15.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Trading systems are highly sensitive to state changes (liquidity, slippage, MEV) and can fail nondeterministically; retries may not be safe without idempotent transaction semantics.","If MCP tool behaviors are not fully specified (inputs/outputs, timeouts, retry policy), agents may produce invalid calls or loop on failures.","If the system executes live trades, ensure the agent has strong guardrails (position limits, approval checks, dry-run modes) and clear separation between simulation and execution."]}}