Supabase

The materials explicitly state that no additional keys or environment variables are required, and there is no visible request for highly sensitive credentials; based on the available facts, the explicit credential exposure surface is small. If runtime behavior relies on an existing local Supabase session or project permissions, access should still be kept to the minimum necessary.

No specific remote endpoint is declared, but the stated functionality—managing tables, querying data, and operating a Supabase project—normally implies communication with the relevant Supabase project service, meaning query contents and project operation requests may be sent there. The materials provide limited transparency on egress targets, so the actual domains and data flows should be verified before use.

The system checks indicate that it executes code, meaning it runs as a local process, which is a standard MCP capability. The available materials do not show requests for unusual system-level privileges, nor execution behavior clearly unrelated to its stated purpose, so this is a normal caution area rather than a high-risk red flag.

Its stated capabilities include table management, data querying, and Supabase project operations, which implies access to database contents and related project resources, with potential to read/write production data or alter project configuration. There is no indication that it needs broad local file access, but permissions on the Supabase-side data plane should be minimized.

The source is platform-curated, with an auditable open-source repository and roughly 2.7k stars of community adoption; these are strong risk-reducing signals. The undeclared license and unknown maintenance status reduce transparency somewhat, but absent other red flags, overall supply-chain risk remains low.