November 2025 Release: Source Tracking, Metrics & Memory Optimization

MCP Server Source Tracking

Every MCP server in your catalog now shows where it came from. A simple badge appears on server details: blue for "Official Registry" or gray for "Manual."

This transparency helps you make better security decisions. Official Registry servers are community-vetted and follow MCP standards, so you can deploy them confidently. Manual servers? Those are custom tools your team built or proprietary integrations specific to your organization. The difference matters when choosing servers.

The tagging happens automatically without any effort on your part. Admins sync servers from the official registry, and they get marked "Official Registry" with no additional configuration required. Create one manually? It's tagged "Manual." Once set, the source can't be changed - you always have an accurate record of where each server originated and who added it to your catalog.

Time-Series Activity Metrics

DeployStack now tracks your MCP client activity over time. No more just seeing total request counts - the system records activity in 15-minute snapshots, showing you exactly when and how your tools get used throughout the day.

Want to know how active your MCP clients were between 10am and 1pm? The system answers that instantly. Which tools did your team use most in the last 3 hours? Easy. The system collects this data automatically every time you use an MCP server, storing it efficiently so performance stays fast.

The metrics system cleans up after itself by removing data older than 3 days automatically. You get clear visibility into recent activity without system slowdowns or storage bloat. Future versions will add more tracking capabilities - server installations, tool execution patterns, and other insights - all built on this same foundation.

Intelligent Process Management

Satellites now save memory by watching for idle stdio-based MCP servers and terminating processes after 3 minutes of inactivity, which frees up about 15MB per server. This prevents your satellite from running out of memory when managing many servers. Need that tool again? It wakes up in 1-2 seconds - you won't even notice the pause.

This changes everything when you run dozens of servers. Previously, 100 MCP servers consumed about 1.5GB of memory continuously - even if you only actively used 10 of them. Now those same 100 servers might use just 150MB when most are dormant. That's a 90% reduction. Your frequently-used tools stay instantly available while rarely-used ones sleep until needed.

The system makes smart decisions about when to sleep processes based on actual usage patterns and workload characteristics. Newly spawned servers get time to initialize. Servers handling active requests never get terminated mid-operation. You can adjust the idle timeout through environment variables - go aggressive on memory savings or keep processes active longer depending on your specific needs and resource constraints. The default 3-minute timeout balances memory efficiency with instant tool availability for most teams.