boxadm-mcp
Related Servers
Alternatives to boxadm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGoogle Workspace security-audit MCP server — read-only visibility into account locks, suspicious logins, and external file sharing, built on the Admin SDK Reports API (audit activities).23252 PyPIMIT
- AlicenseCqualityDmaintenanceA local MCP server for the LimaCharlie security platform that provides investigation, administration, and content-review workflows via a broad read-only tool surface with explicit organization scoping and audit logging.100MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for the SentinelOne management API, exposing sites, endpoint agents, threats, and activity logs with aggregation tools for MSP/MSSP reporting.612 npmMIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for Microsoft Entra ID (Azure AD) that enables querying user sign-in logs, group memberships, and assigned Microsoft 365 licenses via Microsoft Graph API. Provides security and audit visibility without any write operations.-
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server exposing homelab data sources (files, mail, calls) to Cloudflare OS, enabling read-only access to documents, emails, and call records.-
- AlicenseAqualityDmaintenanceA secure, read-only MCP server for AI-powered system monitoring. It provides real-time OS metrics, config discovery, and safe log tailing to enable autonomous infrastructure audits without shell access risks.42ISC
TDQS
Scored across 9 tools
Tools mostly answer clearly distinct questions: raw events versus external-access analytics versus a combined daily brief, and the folder-scan tools return different artifacts (collaborators, open links, owner ranking). Boundaries are well documented; the only minor ambiguity is between daily_brief and its constituent queries.
All tool names are consistently snake_case and descriptive. The set mixes verb-first retrieval names (get_user, list_folder_items) with report-style noun phrases (external_access_events, public_shared_links, top_external_sharers), which is a minor grammatical inconsistency rather than a chaotic pattern.
Nine tools is well within the healthy range for this domain. Each tool adds a distinct audit or visibility query, with one explicitly described convenience composite (daily_brief), so the surface feels deliberately scoped rather than bloated.
The read-only external-exposure/DLP audit surface is strong: raw and aggregated events, external collaborators, public shared links, top external sharers, single-user lookup, folder listing, and health checks. Gaps exist for a full admin lifecycle, notably no remediation/mutation tools (revoking links, removing collaborations, disabling accounts) and no broad directory/account search, though these appear intentional.