io.github.chrischall/ioffice-mcp

The materials show it requires IOFFICE_HOST, IOFFICE_TOKEN, IOFFICE_USERNAME, and IOFFICE_PASSWORD. The token, username, and password are sensitive credentials; if mishandled or exposed in logs, they could be used to access enterprise iOffice accounts and related resources. This is a common integration risk, and no explicit credential-abuse design is evident.

Although no fixed remote endpoint is declared, the presence of the IOFFICE_HOST environment variable indicates the tool connects to a user-specified iOffice host and sends requests related to workspace, rooms, visitors, or tickets. There is no evidence here of data being exfiltrated to unrelated or unknown third-party endpoints.

The system checks explicitly mark executes-code, meaning the MCP tool runs locally as a process and executes its own logic. This is a standard MCP capability; the materials do not show requests for system privileges beyond its stated functionality, so this is rated caution rather than risk.

Based on the description, the tool primarily accesses iOffice business data such as room bookings, visitor management, and maintenance tickets. The materials do not indicate broad local file read/write permissions or obvious over-authorization; however, it may handle enterprise workplace and visitor data, so it should still be treated as business-sensitive access.

The source is an official registry entry, with an auditable open-source repository and updates within the last year, all of which are strong risk-reducing factors. While community adoption is low and the license is undeclared, adding some maintenance and compliance uncertainty, there are no concrete supply-chain red flags in the provided materials.