No user-submitted related servers found.
Scored across 66 tools
Several tools have nearly identical descriptions (e.g., aureon_run_execution and aureon_restore_objective both say 'Run restorative execution for an objective outside policy'), and restoration-related tools (get_restore_plan, propose_restoration, run_execution, restore_objective, confirm_restoration) create unclear boundaries. The many run_*_demo vs get_*_flow pairs add further selection confusion, though some distinct resources like objectives, vault, and reports remain separable.
Almost all tools use the aureon_ prefix followed by consistent snake_case, and verbs (get, list, create, update, prepare, confirm, run) are used predictably. Minor deviations like aureon_me and aureon_ping are not verb_noun, but overall the pattern is highly readable.
With 66 tools, this server is extremely over-scoped, far beyond the typical 3-15 range for a coherent MCP server. The large surface includes many redundant or niche operations that could be consolidated, making selection unwieldy for an agent.
The surface covers extensive lifecycle operations for objectives, executions, settlements, reports, registry, decisions, history, auth, and vault, so few core workflows are missing. Minor gaps exist (e.g., no delete objective or delete/update report), but agents can work around them.
