MCP Server Activity

MCP Server Activity rolls up traffic per governed MCP server for the selected window. Unlike Actor Activity, the row set is anchored on the MCP server catalog itself rather than on observed traffic — every registered server gets a row, including ones with zero invocations in the window, not just servers that happened to receive calls.

distinct_callers counts unique subject_id_hash values that hit the server, regardless of whether those callers are registered agents. It is the same shadow-AI signal used in Actor Activity, but scoped per server — a server with high traffic and a high distinct- caller count relative to its known agent population is calling attention to itself as a possibly under-governed entry point. The policy-mode badge shown per server is read out of the server's spec JSONB blob, since policy mode has no dedicated column on the MCP server table.

Each row also reports invocation count, deny count, summed input and output tokens, and last-active timestamp, sorted by invocation volume and then alphabetically by name.