Microvix

The materials explicitly state that no keys or environment variables are required, and there is no stated need for API keys, passwords, or other highly sensitive credentials. The main concern is not credential exposure here, but possible business account input during actual ERP use.

Network access is declared, with api.mcp.ai as the remote endpoint. Based on the available materials, the tool will likely send requests and business data needed for Microvix ERP interactions to that endpoint; however, the data flow is not documented in detail, so outbound content should be audited and minimized.

System checks indicate that this MCP tool can execute code or spawn local processes. This is a normal capability for this type of tool; the current materials do not show requests for unusual system privileges or actions unrelated to its stated purpose, but it should still be run in a constrained environment.

The documentation does not specify which local files, directories, or system resources can be read or written, so the data-access scope is not transparent. No explicit over-privilege red flag is visible, but as an ERP integration tool it may handle orders, inventory, or store data in practice, so it should be deployed with minimal data exposure.

Positive signals include an official registry source, an auditable open-source repository, and updates within the last year. Caveats are that the README is essentially absent, the license is undeclared, and community stars are 0, limiting documentation quality and community validation; however, the current facts do not justify a high-risk rating.