com.samsung.android.mcfserver Copy

"Samsung Multi Connectivity", the other half of the "mcf" pair on Galaxy devices. Samsung's own Common Criteria application list for the Galaxy S20 5G (G981U, Android 11) records this package under exactly that name at version 1.0.02.85, which is the clearest first-party confirmation of what it is called and that Samsung ships it. It has no Galaxy Store listing, it carries no launcher entry in any observation here, and it is signed by the same Samsung framework key. What it appears to do is manage the radio-level side of connecting to and ranging against nearby devices, leaving the higher-level continuity and handoff behaviour to com.samsung.android.mcfds. The permissions this site records point that way: BLUETOOTH_PRIVILEGED, BLUETOOTH_STACK, START_BLE_PROXY, UWB_RANGING, UWB_PRIVILEGED, NEARBY_WIFI_DEVICES, ACCESS_LOCAL_NETWORK, LOCAL_MAC_ADDRESS, LOCATION_HARDWARE, OVERRIDE_WIFI_CONFIG, NETWORK_SETTINGS, READ_CONTACTS, GET_ACCOUNTS_PRIVILEGED and WRITE_SECURE_SETTINGS. Samsung publishes no functional description of the package, so that reading is inferred from the permissions and the shared naming, not stated by Samsung. Version note: builds recorded here run from 1.2.02.8 to 4.6.11.11, targeting API 32 to 36. Because the newest build string is identical to com.samsung.android.mcfds, the two look like one versioned component set on current devices, even though the S20 list shows this package shipping on Android 11 without its partner. Nothing sourced here explains what changed between those points, so treat the pairing as a current-device observation rather than a stable rule across releases. For Android Enterprise, EMM and kiosk work, treat it as infrastructure for Samsung's device-to-device features rather than a feature in its own right. It has no user interface to lock down and no Knox Service Plugin restriction of its own. If the goal is to stop cross-device sharing on a managed handset, the practical levers are the documented feature-level and application-level controls rather than this package, and Knox Manage's application policies are the documented route to block it by name. Caution rather than safe: removing a connectivity service that other Samsung components call into can have effects beyond the feature you meant to remove, and none of those effects are documented, so test before rolling out.

• Galaxy S20 5G (G981U) application list - Samsung Knox CC Mode documentation →
• Device restrictions - Knox Service Plugin - Samsung Knox Documentation →
• Enable or disable a specific system app - Knox Manage - Samsung Knox Documentation →
• Package provenance for com.samsung.android.mcfserver - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, and that single certificate is consistent across all 19 device profiles. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 38 permissions: 7 runtime (user-granted), 13 signature or system-level, 7 install-time and 11 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.