No user-submitted related servers found.
Scored across 35 tools
The tool set is large but largely distinct: memory lifecycle, messaging, governance, tasks, and federation each have their own tools. The messaging cluster (sage_inbox, sage_messages_receive, sage_message_history, sage_message_replies, sage_message_status) has the most overlap, but descriptions explicitly differentiate their roles (claiming vs unified update surface vs browsing vs sender-side paging). An agent could still confuse inbox and receive at first glance, so it is not perfect.
All tools share a consistent sage_ prefix and snake_case style, making them recognizable. However, the internal pattern is mixed: some are verb-first (sage_get_links, sage_find_agent), some noun-first (sage_scope_get, sage_message_send), and some single words (sage_remember, sage_inbox, sage_recall). This is readable but not a uniform convention.
With 35 tools, this server is heavy for a single MCP surface. While the domain (persistent memory, messaging, governance, federation) is broad, the count exceeds the typical well-scoped range and forces agents to navigate many overlapping-sounding entry points.
The surface covers registration, identity, memory CRUD (with replacement via sage_remember), recall, linking, corroboration, tasks, messaging, governance, scopes, and federation discovery. Minor gaps exist—no explicit memory update tool (handled by replacement) and no message retraction/delete—but these appear intentional or workable.
